[blag-whereto] BLAG Trac #33: Developer page

[BLAG]

#33: Developer page
-----------------------+----------------------------------------------------
 Reporter:  r7         |       Owner:  r7      
     Type:  Wiki page  |      Status:  assigned
 Priority:  minor      |   Milestone:          
Component:  BLAG Wiki  |     Version:          
 Keywords:  wiki       |  
-----------------------+----------------------------------------------------

Comment(by jayeola):

 suggested headings:-

 = Background =
 This section(s) spells out the History of BLAG, where and how it got here.
 Give credit to Jebba for maintaining so much of the work single handedly.

 = Objectives =
 This section spells out what we are aiming to do and why. Helps to know
 what the project is about from a "high level perspective", without having
 to read lots of code, docs and emails.

 = Infrastructure =
 What we have without giving away too much detail ;-)
  * This (e.g. Blue Gene)
  * That (E.g. Cray)
  * The other (E.g. NASA when no one is looking)

 = Wish List =
 Stuff that we may want but do not have yet. Eg. , Any hardware/bandwidth
 that we need. etc etc
  * World Peace Servers
  * Anti-Corruption Bandwidth
  * BLAG World Domination
  * /me in control
  * 1 24xport switch
  * 1 1U server dual-core for testing packages.


 = Roadmap =
  * Include 10k to 90k (list dates and releases
  * 10000 Month/year
  * etc
  * __Current__ BLAG version
  * Next __alpha__ BLAG version  - target date (if applicable)
  * Next __stable__ BLAG version  - target date (if applicable)

  __OR__

 keep this page:- https://blag.wiki.aktivix.org/Roadmap


 = Team roles/functions =
 This helps to split the work into definate "''manageable'' chunks" for
 people to do. I know that this may sound like "corporate speak", but it'll
 be easier for new comers to see a function or role and fit into it than to
 see a large project and be __overwhelmed__ by it. [Hard to know where to
 start sometimes].


 Title and short descrition of what person typically does eg;
 == Maintainer ==
 The maintainer does this and does that. S/he works closely with the ?? and
 ?? to do blah blah

 Tools used are;
  * This tool (rpmbuildtools, mock etc)
  * That tool
  * etc

 == Packager ==
 Does what ever s/he does. Works closely with the ?? to ensure that this
 does that.

 Tools used are;
  * This tool
  * That tool
  * etc

 == Techical writer / documentor ==
 This chap writes __simple__ guides and howtos. The detail and level of
 complexity of this documentation is determined by the target audience.
 Also makes logs of techical discussions and issues them to the correct
 place, (forums, mailing list, server log etc).

 Tools used are;
  * This tool
  * That tool
  * etc

 == Package builder ==
 Builds packages for BLAG GNU/Linux and weeps at his keyboard.

 Tools used are;
  * This tool (e.g coffee)
  * That tool (e.g thick skin)
  * etc

 == Package (re)builder ==
 The package (re)builder does.... and works closely with ...
 Tools used are;
  * This tool
  * That tool
  * etc

 == Package tester ==
 The package tester tests rpms for BLAG on his machine and reports back to
 ?? detailing what does or does not work.

 Tools used are;
  * This tool
  * That tool
  * etc

 == OS Tester ==
 The OS tester tests spins of BLAG on his machine and reports back to ??
 detailing what does or does not work.

 Tools used are;
  * This tool
  * That toool
  * etc


 == Release chap ==
 This chap writes announcements to the public to say that a new spin or
 release of BLAG GNU/Linux is ''''ready''' for the world. Announcements can
 be made to:-
  * Forums
    * forums.blagblagblag.org
    * linuxquestions.org,
    * insert more forums here
  * Mailing lists
    * Long list of mailing lists here
  * Web sites
    * blag's site
    * linuxquestions.org
    * distrowatch.com
    * long list of web sites here
  * Linux User Groups
    * Long list of LUG's here
  * Free Software Mirrors
    * Ibiblo
    * Your college, school or org
  * Torrents!
    * Get in touch with the server guy and the mirror chap. Tell them to
 seed, seed, seed.
  * The press
    * Linux Format
    * Insert your fave mag here (__Send__ them a CD and ask them to play
 ;))

 == Artwork & Eye Candy ==
 We want BLAG to look __good__! So if you can help, roll up your sleeves
 and get out your digital paint brushes ;-)
 Tools used are;
  * This tool (E.g. expected format)
  * That tool (E.g. expected sizes)
  * etc

 == Server Maintainers ==
 As a server maintainer we would like to to maintain the server. Expect to
 allow the builders, testers and ?? ssh access into this server.
 Tools used are;
  * This tool
  * That tool
  * etc

 == Mirror Maintainers ==
 As a mirror maintainer we would like to to mirror the server. Please liase
 with the _server maintainer_ to ensure that you mirror is upto date by
 synching every X hours,days etc.
 Tools used are;
  * This tool (E.g. rsync)
  * That tool (E.g Git)
  * etc


 = Suggestions =
 We would gladly like to recieve your comments and suggestions whilst we
 make BLAG the best distro there is. Hola.


 == Communications ==
 Those invloved in the development of BLAG GNU/Linux use the following
 methods to communicate;
  * Mailman mailing list hosted by AktiviX. Called [blag-whereto].
  * channel #blag @irc.indymedia.org, port 6667.
  * This thing
  * That thing
  * Telepathy
  * Peace and Love

-- 
Ticket URL: <http://trac.slated.org/ticket/33#comment:2>
BLAG <http://www.blagblagblag.org/>
BLAG Linux and GNU