Size: 97
Comment: started
|
Size: 4720
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
Most of the stuff regarding webmaster work is described at http://www.debian.org/devel/website/ | #language en ||<tablestyle="width: 100%;" style="border: 0px hidden">~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: none-~||<style="text-align: right;border: 0px hidden"> (!) [[/Discussion|Discussion]]|| ---- == Infrastructure == * '''Website''': http://www.debian.org/devel/website/ * '''Documentation''': http://www.debian.org/devel/website/desc * '''Unix group''': webwml, debwww, pkg_maint * Services handled by the team: * /srv/www.debian.org/ on www-master.debian.org http://www.debian.org/ (wolkenstein.d.o) * /srv/search.debian.org/ on http://search.debian.org/ (senfl.d.o) * /srv/cgi.debian.org/ on cgi.debian.org (master.d.o) * /srv/packages.debian.org/ on http://packages.debian.org/ (powell.d.o) - related but different team/permissions Most of the stuff regarding webmaster work is described at the aforementioned web site and all prospective editors are highly recommended to read it. == Interacting with the team == * '''Read the docs first''': http://www.debian.org/devel/website/ * '''Email contact''': * <<MailTo(debian-www AT lists DOT debian DOT org)>> - mailing list for most inquiries * consultants@d.o, cdvendors@d.o, merchandise@d.o - aliases for those particular things that need input from outsiders * webmaster@d.o for debwww-only stuff, and whatever random crap ;) * '''Request tracker''': http://bugs.debian.org/www.debian.org == Usual roles == All work is shared in two teams: * people in the debwww group - particular webmaster-only stuff * people in the webwml group - everything reachable via webwml CVS The webwml CVS/group does the bulk of the editing. The debwww Unix group handles the bits necessary for webwml to propagate onto the web site, CGI scripts, and similar intricate details. You can [[https://alioth.debian.org/project/request.php?group_id=1135|request CVS commit access]] through the alioth project, please fill in the comment box with a reasoning. == Get involved == You are skilled in design/CSS or coding/Perl, know about the firebug/webdeveloper toolbars, are ready to understand required constraints of debian.org websites and want to make them clearer and improve navigation? Join us, there are plenty of bugs[bug] to solve and improvement to be achieved. Even if you don't see yourself in the above mentioned skills, you still can help the web team in various ways: People working on the content of specific subparts (like events pages, users or consultants subareas) are also very welcome. You don't need much knowledge about the above mentioned parts, just being willing to dig into stuff and invest a bit of time every now and then. So, if you want to join the webteam the first step is subscribe our [[http://lists.debian.org/debian-www/|mailing list]] and join the team IRC channel {{{debian-www}}} at {{{irc.debian.org}}}. Below you can found a list of tasks to be done, in order of difficulty: take a look and feel free to submit a patch. :) * <<Icon(star_on.png)>> __Easy tasks__ Here's some easy bugs (if you have not experience on how to manage bug reports, please read [[HowtoUseBTS|this tutorial]] and the documentation on the website, like http://www.debian.org/Bugs/Developer): DebianBug:363496 :contact authors of book listed at http://www.debian.org/doc/books, collect year of publication/last edition of each book and add it to the page DebianBug:317140 :add in http://www.debian.org/doc/books the license for each book DebianBug:381555 :add a link to md5sum and/or SHA1SUM and SHA1SUM.sign files at http://www.debian.org/distrib/netinst DebianBug:347922 :create a page on how to write an installation report (see the installation manual and keep in touch with d-i people). DebianBug:489027 :fix http://www.debian.org/Bugs/server-refcard to show only "thanks" (instead of "thanks...") and link full and complete documentation for that command in http://www.debian.org/Bugs/server-control#thanks * <<Icon(star_on.png)>><<Icon(star_on.png)>> __Medium tasks__ DebianBug:510894 :if you want to fix this you need some Perl knowledge and you have to be very careful: the risk is to break out part of the site. * <<Icon(star_on.png)>><<Icon(star_on.png)>><<Icon(star_on.png)>> __Difficult tasks__ ##== More stuff == ##''If you have no other dedicated place to document stuff concerning your team, then use this place. You can put documentation (with warnings<<Icon(alert.png)>> and ##infos<<Icon(icon-info.png)>>), FAQ, TODO list (see "Get Involved" above) , ideas (<<Icon(idea.png)>>) etc.'' ##''You can use [[/Subpages|Subpages]] to structure the content if you have many things to document here.'' |
Infrastructure
Website: http://www.debian.org/devel/website/
Documentation: http://www.debian.org/devel/website/desc
Unix group: webwml, debwww, pkg_maint
- Services handled by the team:
/srv/www.debian.org/ on www-master.debian.org http://www.debian.org/ (wolkenstein.d.o)
/srv/search.debian.org/ on http://search.debian.org/ (senfl.d.o)
- /srv/cgi.debian.org/ on cgi.debian.org (master.d.o)
/srv/packages.debian.org/ on http://packages.debian.org/ (powell.d.o) - related but different team/permissions
Most of the stuff regarding webmaster work is described at the aforementioned web site and all prospective editors are highly recommended to read it.
Interacting with the team
Read the docs first: http://www.debian.org/devel/website/
Email contact:
<debian-www AT lists DOT debian DOT org> - mailing list for most inquiries
consultants@d.o, cdvendors@d.o, merchandise@d.o - aliases for those particular things that need input from outsiders
webmaster@d.o for debwww-only stuff, and whatever random crap
Request tracker: http://bugs.debian.org/www.debian.org
Usual roles
All work is shared in two teams:
- people in the debwww group - particular webmaster-only stuff
- people in the webwml group - everything reachable via webwml CVS
The webwml CVS/group does the bulk of the editing. The debwww Unix group handles the bits necessary for webwml to propagate onto the web site, CGI scripts, and similar intricate details.
You can request CVS commit access through the alioth project, please fill in the comment box with a reasoning.
Get involved
You are skilled in design/CSS or coding/Perl, know about the firebug/webdeveloper toolbars, are ready to understand required constraints of debian.org websites and want to make them clearer and improve navigation? Join us, there are plenty of bugs[bug] to solve and improvement to be achieved.
Even if you don't see yourself in the above mentioned skills, you still can help the web team in various ways: People working on the content of specific subparts (like events pages, users or consultants subareas) are also very welcome. You don't need much knowledge about the above mentioned parts, just being willing to dig into stuff and invest a bit of time every now and then.
So, if you want to join the webteam the first step is subscribe our mailing list and join the team IRC channel debian-www at irc.debian.org.
Below you can found a list of tasks to be done, in order of difficulty: take a look and feel free to submit a patch.
Easy tasks
Here's some easy bugs (if you have not experience on how to manage bug reports, please read this tutorial and the documentation on the website, like http://www.debian.org/Bugs/Developer):
363496 :contact authors of book listed at http://www.debian.org/doc/books, collect year of publication/last edition of each book and add it to the page
317140 :add in http://www.debian.org/doc/books the license for each book
381555 :add a link to md5sum and/or SHA1SUM and SHA1SUM.sign files at http://www.debian.org/distrib/netinst
347922 :create a page on how to write an installation report (see the installation manual and keep in touch with d-i people).
489027 :fix http://www.debian.org/Bugs/server-refcard to show only "thanks" (instead of "thanks...") and link full and complete documentation for that command in http://www.debian.org/Bugs/server-control#thanks
Medium tasks
510894 :if you want to fix this you need some Perl knowledge and you have to be very careful: the risk is to break out part of the site.
Difficult tasks