The Open-Bloggers Declaration:

1.any admins will have each others public/private OpenGPG key-pairs. Good thing it is so dirt simple in Linux. These keys will be used to verify(sign) Documents, code, encrypted volumes with your digital key. This makes it so admins have basically pvt. encrypted digital message communications.

#I gave my first guest Blogger/new admin a break, because A)I havn’t written those Blogs quite #yet, but also that he is helping to clean up the organization of the code. Possibly with #Joomla(I’m not fully sure)?

2.I want to make sure that all admins have a strong cipher(a password card-second factor authentication is highly recommended, to help you remember your passwords; and if the card gets nabbed random humans can’t read your passwords)for your main trueCrypt volume &&  they can use for their encrypted volumes(show up as open drives once unlocked). TrueCrypt is the prefered choice for this. The installer for trueCrypt is the same for almost all Linux/mac computers in that it is just a bash install command to install it. It is also open-source, and as long as there is Internet, there will be surviving open-source projects thriving.

3.all admin/guest bloggers must sign the Ubuntu code of conduct on launchpad. Must be signed with your public key. verified through the public key-servers.

4.I believe that admins and guest Bloggers should both contribute both A)original self-created posts, and take part in @ least some of the collaboration efforts.

5.I prefer that all admins use some sort of password protected pass-word dataBase such as keepass2(possibly more windows compatible), or keePassX(only really Linux compatible) within an encrypted volume. Because you would be using your own encryption before sending it to a cloud-service, that would be allowed.

#I use Ubuntu one myself

I have nothing against LastPass, as long as you don’t remember the password.

(I copy/paste from my local password dataBase, and after I am logged in all internet sites are one click auto-fill usually-98% of the time)

6.I want this Declaration to extend far beyond just open-source construction. I want This to serve as a guide for Internet security standards, behavior standards, and trying to be as helpful to the community as possible.

7. No foul, or language you can’t speak around your Mother.

8. No Link baiting aka smearing an open-source project, just for ratings...

For standards of behaviour/conduct I am copy/pasting in the Ubuntu code-of-conduct on the next page for us to collaborate on.

.

Ubuntu is an African concept of 'humanity towards others'.

This Code of Conduct covers our behaviour as members of the Ubuntu Community, in any forum, mailing list, wiki, web site, IRC channel, install-fest, public meeting or private correspondence. Ubuntu governance bodies are ultimately accountable to the Ubuntu Community Council and will arbitrate in any dispute over the conduct of a member of the community.

• Be considerate. Our work will be used by other people, and we in turn will depend on the work of others. Any decision we take will affect users and colleagues, and we should take those consequences into account when making decisions. Ubuntu has millions of users and thousands of contributors. Even if it's not obvious at the time, our contributions to Ubuntu will impact the work of others. For example, changes to code, infrastructure, policy, documentation, and translations during a release may negatively impact others' work.
• Be respectful. The Ubuntu community and its members treat one another with respect. Everyone can make a valuable contribution to Ubuntu. We may not always agree, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the Ubuntu community to be respectful when dealing with other contributors as well as with people outside the Ubuntu project and with users of Ubuntu.
• Be collaborative. Collaboration is central to Ubuntu and to the larger free software community. This collaboration involves individuals working with others in teams within Ubuntu, teams working with each other within Ubuntu, and individuals and teams within Ubuntu working with other projects outside. This collaboration reduces redundancy, and improves the quality of our work. Internally and externally, we should always be open to collaboration. Wherever possible, we should work closely with upstream projects and others in the free software community to coordinate our technical, advocacy, documentation, and other work. Our work should be done transparently and we should involve as many interested parties as early as possible. If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress.
• When we disagree, we consult others. Disagreements, both social and technical, happen all the time and the Ubuntu community is no exception. It is important that we resolve disagreements and differing views constructively and with the help of the community and community processes. We have the Technical Board, the Community Council, and a series of other governance bodies which help to decide the right course for Ubuntu. There are also several Project Teams and Team Leaders, who may be able to help us figure out the best direction for Ubuntu. When our goals differ dramatically, we encourage the creation of alternative sets of packages, or derivative distributions, using the Ubuntu Package Management framework, so that the community can test new ideas and contribute to the discussion.
• When we are unsure, we ask for help. Nobody knows everything, and nobody is expected to be perfect in the Ubuntu community. Asking questions avoids many problems down the road, and so questions are encouraged. Those who are asked questions should be responsive and helpful. However, when asking a question, care must be taken to do so in an appropriate forum.
• Step down considerately. Members of every project come and go and Ubuntu is no different. When somebody leaves or disengages from the project, in whole or in part, we ask that they do so in a way that minimises disruption to the project. This means they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off.

We pride ourselves on building a productive, happy and agile community that can welcome new ideas in a complex field, and foster collaboration between groups with very different needs, interests and goals. We hold our leaders to an even higher standard, in the Leadership Code of Conduct, and arrange the governance of the community to ensure that issues can be raised with leaders who are engaged, interested and competent to help resolve them.

Mailing lists and web forums

Mailing lists and web forums are an important part of the Ubuntu community platform. This code of conduct applies to your behaviour in those forums too. Please follow these guidelines in addition to the general code of conduct:

1. Please use a valid email address to which direct responses can be made.
2. Please avoid flamewars, trolling, personal attacks, and repetitive arguments. On technical matters, the Technical Review Board can make a final decision. On matters of community governance, the Community Council can make a final decision.

Positive conduct:

>Requesting a chance to wrestle the issue out in private.

>add comments of the material you are sharing

Here is a list I created of people who were on my lists for whatever reason that might be interested to sign up with the open-Blogger Declaration. These are commercial persuits, fun, sharing freedom, distro-review, Local area User goups, on-line magazines, tweaks from beginer through advanced. Some people on that list lead a large following on the InterWebs.

list of open-source bloggers:

DarkDuck

iloveubuntu

iheartubuntu

ubuntu vibes

linuxMag

rothgar

jono bacon

command line magic

eff

Linux alert

upUbuntu Blog

MukTware

InfinitelyGalactic

Unixmen

Linux for You

linuxaria

ubuntu training team

Jason Gerard DeRose

open-govt.

ubuntu tribe

omgSUSE

python software foundation

Ubuntu developers

ohio linux group

boston user group

>LA users group

Ubuntu manual

nixCraft

Linux User&Developer Daily

VIM-tips

the Linux outlaws

nixie pixel

tuxRadar

oscon

mintCast

LinuxPro

Linuxmagazine

Linuxjournal

the linux foundation

Bryan Lunduke

Jason Applebaum/Shannon Morse/Darren Kitchen

LvL1

chris/angela fisher

omgUbuntu

tuxtrix

the document foundation

scribus

Aaron Seigo/jeff hoagland/Linux grandma

canonical/

Linux Netbook/vijeenrosh

chris hoffman

phoronix