/[gentoo]/xml/htdocs/proj/en/glep/glep-0030.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0030.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.3
1GLEP: 30 1GLEP: 30
2Title: "Planet Gentoo" web log aggregator 2Title: "Planet Gentoo" web log aggregator
3Version: $Revision: 1.1 $ 3Version: $Revision: 1.3 $
4Last-Modified: $Date: 2004/10/26 00:18:41 $ 4Last-Modified: $Date: 2004/11/10 16:15:34 $
5Author: Daniel Drake <dsd@gentoo.org> 5Author: Daniel Drake <dsd@gentoo.org>
6Status: Draft 6Status: Draft
7Type: Standards Track 7Type: Standards Track
8Content-Type: text/x-rst 8Content-Type: text/x-rst
9Created: 24-Oct-2004 9Created: 24-Oct-2004
10Post-History: 25-Oct-2004 10Post-History: 25-Oct-2004, 10-Nov-2004
11 11
12Credits 12Credits
13======= 13=======
14- `Stuart Herbert`_ for the original idea 14- `Stuart Herbert`_ for the original idea
15- `Alexander Plank`_ who also has put effort into promoting this 15- `Alexander Plank`_ who also has put effort into promoting this
45Readers would get more interested in the Gentoo project, and would get a feel 45Readers would get more interested in the Gentoo project, and would get a feel
46for the personalities of the contributing developers. Although I am not 46for the personalities of the contributing developers. Although I am not
47suggesting this should be used as an announcement tool, developers could also 47suggesting this should be used as an announcement tool, developers could also
48use this to get general messages over to the user community. 48use this to get general messages over to the user community.
49 49
50This would also benefit our development, as developers would also be able to
51keep track of what other developers are working on and promote more
52collaboration amongst each other.
53
50Specification 54Specification
51============= 55=============
52 56
53The proposed design is an installation of Planetplanet at a part of the 57The proposed design is an installation of `Planetplanet`_ at a part of the
54gentoo.org infrastructure, e.g. http://planet.gentoo.org 58gentoo.org infrastructure, e.g. http://planet.gentoo.org
55 59
56We would also provide an installation of `Wordpress`_ or a similar weblogging 60We would also provide an installation of `Wordpress`_ or a similar weblogging
57engine, for developers that do not have their own weblog or would wish to 61engine, for developers that do not have their own weblog or would wish to
58move their log to an official Gentoo hosted website. This could be provided 62move their log to an official Gentoo hosted website. This could be provided
65executed as a cronjob and fetches content from all the weblogs it has been 69executed as a cronjob and fetches content from all the weblogs it has been
66asked to, postprocesses and aggregates them into a single html file (based on 70asked to, postprocesses and aggregates them into a single html file (based on
67a template), and outputs that html content to an area provided by a webserver. 71a template), and outputs that html content to an area provided by a webserver.
68This should allow for ease of integration with any existing infrastructure. 72This should allow for ease of integration with any existing infrastructure.
69 73
74Planetplanet is configurable through a single configuration file, which lists
75the log feed URL, real name and user name for each contributing developer.
76
77`Wordpress`_ is a weblogging engine written in PHP. It relies on MySQL for
78the data store. After the initial setup, all configuration is done through a
79web-based interface.
80
70A group of people would be assigned the responsibility/CVS access to maintain 81A group of people would be assigned the responsibility/CVS access to maintain
71the planetplanet configuration file, which lists the developers weblogs to be 82these two services. I would suggest the existing infrastructure team to have
72aggregated. They would also be required to maintain the weblog engine 83this responsibility. If required, I will assist with the initial
73provided, this is done through a web-based administration interface. I would 84configuration.
74suggest the existing infrastructure team to have this responsibility.
75 85
76The planetplanet installation would fetch and aggregate developers weblogs 86The planetplanet installation would fetch and aggregate developers weblogs
77only, we would not accept non-developer logs. 87only, we would not accept non-developer logs.
78 88
79Developers do not have to host their weblogs with us, practically all blogging 89Developers do not have to host their weblogs with us, practically all blogging
80packages provide an XML feed (typically RSS) which planetplanet will happily 90packages provide an XML feed (typically RSS) which planetplanet will happily
81fetch and process. Other feed formats are also accepted, examine the 91fetch and process. Other feed formats are also accepted, examine the
82planetplanet documentation for more info. 92planetplanet documentation for more info.
93In the event of a contributing Gentoo developer leaving the project, their log
94would be removed from the aggregation. If their log was hosted by ourselves,
95it would be closed. For this reason, some developers may choose to host their
96log elsewhere - this is not a problem and is left to the decision of the
97individual developers.
98
99It is true that the addition of the planet to our website collection would add
100yet another source of Gentoo information to our collection; our users and
101developers are already overwhelmed with IRC, mailing lists, forums, and the
102central website. In contrast, a lot of information is currently replicated
103over those mediums, but the planet would provide a taste of something new.
104Developers can choose their own topics and are free to write about things that
105perhaps would not fit into our existing communication mediums. Additionally,
106the planet will attempt to bring some existing content together by linking to
107recent commits, bug lists, and dev.gentoo.org webspace for each contributing
108developer.
83 109
84It has been suggested that the activity of the planet may be an issue: 110It has been suggested that the activity of the planet may be an issue:
85although a lot of activity would make the planet very successful, it may look 111although a lot of activity would make the planet very successful, it may look
86bad on us as a whole if the planet is inactive. 112bad on us as a whole if the planet is inactive.
87 113
102short space of time, and it was only mentioned once in a rather large thread 128short space of time, and it was only mentioned once in a rather large thread
103on the gentoo-dev mailing list. I predict that given more publicity amongst 129on the gentoo-dev mailing list. I predict that given more publicity amongst
104the developers, this idea would be even more popular. I also predict that if 130the developers, this idea would be even more popular. I also predict that if
105such a planet were to go live, other developers would be motivated to join in, 131such a planet were to go live, other developers would be motivated to join in,
106and new developers joining the project would be keen on contributing. 132and new developers joining the project would be keen on contributing.
133
134The success of the planet will be evaluated by examining the number of hits to
135the planet. 3 months after launch, one weeks worth of logs will be recorded,
136and hits will be counted. If the hit count for that week is below 1000, the
137planet will be deemed as not having met its target, and appropriate action can
138be taken if the planet appears to be harming our image.
107 139
108Backwards Compatibility 140Backwards Compatibility
109======================= 141=======================
110 142
111No issues. 143No issues.

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.3

  ViewVC Help
Powered by ViewVC 1.1.20