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