1 |
grr, sent as wrong sender again... |
2 |
|
3 |
On Wed, Apr 23, 2008 at 1:57 PM, Alec Warner <antarus@×××××××××××.com> wrote: |
4 |
> On Wed, Apr 23, 2008 at 9:58 AM, Nirbheek Chauhan |
5 |
> <nirbheek.chauhan@×××××.com> wrote: |
6 |
> > On Tue, Apr 22, 2008 at 11:33 PM, Anant Narayanan <anant@g.o> wrote: |
7 |
> > [snip an awesome project] |
8 |
> > |
9 |
> > |
10 |
> > > Automate it All |
11 |
> > > by Nirbheek Chauhan |
12 |
> > |
13 |
> > It's "Automate it All"! =P |
14 |
> > The quotes are important. =) |
15 |
> > |
16 |
> > [snip other awesome projects] |
17 |
> > |
18 |
> > [snip some great advice] |
19 |
> > |
20 |
> > |
21 |
> > |
22 |
> > > - Blogs: A lot of developers use blogs to communicate with the |
23 |
> > > community at large. We recommend you read posts on Planet Gentoo |
24 |
> > > (http://planet.gentoo.org/) and add the feed to your reader. We also highly |
25 |
> > > recommend that you get a blog for yourself (if you already don't have one), |
26 |
> > > and use it to write anything relevant to your project under a category such |
27 |
> > > as 'soc08' or 'gentoo'. We will be aggregating your blogs on our Planet for |
28 |
> > > the entire Gentoo community to read. |
29 |
> > |
30 |
> > Besides planet gentoo, there's also http://planet-soc.com -- the |
31 |
> > official GSoC planet :) |
32 |
> |
33 |
> I encourage you to sign up for both. You can contant |
34 |
> planet@g.o for us and I'm sure planet-soc has some signup |
35 |
> somewhere (the le' awesome webchick is running it). |
36 |
> |
37 |
> |
38 |
> > |
39 |
> > |
40 |
> > > |
41 |
> > > Code Management |
42 |
> > > - Gentoo uses a mix of CVS, SVN and Git internally. We recommend you |
43 |
> > > use an external code hosting service to help manage your code. Some of the |
44 |
> > > popular ones are: http://code.google.com/hosting/(SVN), |
45 |
> > > http://sourceforge.net/ (CVS/SVN) and http://repo.or.cz/ (Git). |
46 |
> > |
47 |
> > Using external code hosting services makes keeping track of all the |
48 |
> > Gentoo projects painful at the very least. Some people will use |
49 |
> > code.google, others sf, launchpad, etc etc and one has to run around |
50 |
> > between all these websites to access the projects. |
51 |
> |
52 |
> Painful at the very least eh? I disagree ;) |
53 |
> |
54 |
> I expect students to use whatever hosting service they choose provided |
55 |
> it is up enough (ie hosting it on your workstation at home is probably |
56 |
> not good enough). |
57 |
> |
58 |
> I expect students to post a URL to their code somewhere so people can |
59 |
> find it easily (maybe we can update the soc webpage...). |
60 |
> |
61 |
> You may want to visit the 'official' unofficial soc wiki as well: |
62 |
> |
63 |
> 13:54 <@antarus|work> !wiki |
64 |
> 13:54 <+socinfo> "wiki" is located at http://socwiki.natulte.net/ . For |
65 |
> accepted SoC students only, see the student list for access |
66 |
> information! |
67 |
> |
68 |
> |
69 |
> > |
70 |
> > So to make things easier for the students, mentors, and those who are |
71 |
> > interested in the code, Redmine has been setup at |
72 |
> > http://soc.gentooexperimental.org/ (hosting courtesy bonsakitten) for |
73 |
> > Gentoo SoC project management. |
74 |
> > |
75 |
> > Redmine was chosen over Trac for the following reasons: |
76 |
> > |
77 |
> > 1. Hosting multiple projects is trivial with Redmine compared to Trac |
78 |
> > 2. Redmine is *simple*. |
79 |
> > 3. Redmine doesn't provide inbuilt source code management, and instead |
80 |
> > can "watch" any repository you want. This makes managing projects |
81 |
> > which already have an exisiting repostory (such as portage for the |
82 |
> > revdep-rebuild project) very easily |
83 |
> > 4. Redmine provides a wiki, a forum, a bug tracker, release cycle, |
84 |
> > calendar for planning, fancy charts for stats, and will provide a |
85 |
> > mailing list in a future release. |
86 |
> > |
87 |
> > Redmine can manage bzr, svn, cvs, git, darcs, and mercurial repositories |
88 |
> > |
89 |
> > bzr, svn, and git repository management will be provided on the same |
90 |
> > server for projects that need it. |
91 |
> > |
92 |
> |
93 |
> Thanks go to Patrick and Co. for getting this set up. I want to |
94 |
> stress again that while it is utterly awesome that it is offered, you |
95 |
> don't have to use it. |
96 |
> |
97 |
> |
98 |
> > |
99 |
> > > One of the |
100 |
> > > explicit aims of the Community Bonding period is to get you upto speed with |
101 |
> > > the version control system you will be working with. Please contact your |
102 |
> > > mentor for help *before* signing up with a particular service. In some |
103 |
> > > cases, you may be expected to work on an existing repository - again - |
104 |
> > > contact your mentor for specifics. |
105 |
> > |
106 |
> > [snip more great advice] |
107 |
> > |
108 |
> > |
109 |
> > > |
110 |
> > > Alec Warner: antarus@g.o |
111 |
> > > Grant Goodyear: g2boojum@g.o |
112 |
> > > Joshua Jackson: tsunam@g.o |
113 |
> > |
114 |
> > What do the powers that be have to say about soc.ge.o? Can we have it |
115 |
> > as the official project management place for Gentoo SoC projects? :-) |
116 |
> |
117 |
> I don't think an 'official' place is necessary but feel free to try to |
118 |
> convince me otherwise. |
119 |
> |
120 |
> -Alec |
121 |
> |
122 |
> |
123 |
> |
124 |
> > |
125 |
> > If so, Anant might want to add this to the GSoC section in this month's GMN ;-) |
126 |
> > |
127 |
> > |
128 |
> > -- |
129 |
> > ~Nirbheek Chauhan |
130 |
> > -- |
131 |
> > |
132 |
> > |
133 |
> > gentoo-soc@l.g.o mailing list |
134 |
> > |
135 |
> > |
136 |
> |
137 |
-- |
138 |
gentoo-soc@l.g.o mailing list |