By the way. When migrating our documentation over to the new wiki I
merged some of the documentation.
"Pat's notes on eclipse" merged into "Eclipse API notes"
"Configuring your Eclipse target" merged into "Eclipse API notes"
"Paul's Notes on Subclipse" moved into "General Notes"
I didn't migrate the milestones becuase I figured if you're interested you
can submit those as bug/feature items on sourceforge and these should
probably be managed from there from here on out.
I think that about sums it up.
--
Drew
On Sat, 2 Aug 2008, Andrew Case wrote:
> Yes it's also important that only people who we want to have admin access
> to things end up with gitclipse shell access. I think only "Admin"
> members get shell access to the group by default. So as long as
> permissions stay only user/group readable it should be fine.
>
> I struggled with the wiki idea, but I ended up thinking the the ease of
> gitclipse members/users to be able to contribute outweighed the extra work
> to manage it. It might be over doing it for gitclipse, but we'll see.
>
> Speaking of documentation...
>
> Gitclipsers,
>
> At some point we need to write some proper help, install, build, tutorial,
> contribute documentation for the plug-in. Of course the code
> functionality is currently more crucial so we have some working software,
> but proper documentation is also critical for a projects success. Maybe
> if each of us volunteer to take on one of these topics, we'll have at
> least decent documentation for our alpha release.
>
> I'd like to volunteer for the contribution documentation, otherwise it
> seems like it would make sense for the following users to work on these
> documentation parts (in my mind at least):
> Build - Michelle (since you managed CC you have the most experience)
> Install - Patrick (since you're setting up the update-site)
> Help (accessed from inside eclipse) - Paul or Han?
> Tutorial (something simple, just how to checkout/init/import a project
> modify and then commit it) - Paul or Han?
>
> If someone doesn't think they can manage it with their current work load,
> this shouldn't be a problem, but please let us (gitclipse-devel) know.
> Since obviously some documentation is more important than others so we
> might need to shuffle ownership to make sure the more important ones get
> done.
>
> Thanks!
>
> --
> Drew
>
>
> On Fri, 1 Aug 2008, James Linder wrote:
>
>> Hey Andrew,
>>
>> I like that idea. So long as we are careful to make the README user
>> and group readable, it works nicely.
>>
>> All,
>>
>> I'm working on doing a similar migration for javagit notes.
>>
>> The file 'shell.sourceforge.net:/home/groups/j/ja/javagit/README' now
>> contains the resource information. It is accessible only to users in
>> the javagit members granted shell access to the javagit group.
>>
>> I've added a number of feature requests and bugs from the information
>> in the wiki. I don't plan on creating a JavaGit wiki at the moment;
>> perhaps we'll do that a little later. For now, I'll move the
>> appropriate information into the website pages.
>>
>> Cheers,
>>
>> James
>>
>>
>> On Aug 1, 2008, at 4:27 PM, Andrew Case wrote:
>>
>>> In an effort to move our project into public space I'm migrating
>>> more things over to sourceforge.
>>>
>>> The most important of which is probably the info from the "Project
>>> Resoures" wiki page. The new location for this documentation is
>>> available through ssh at 'shell.sourceforge.net:/home/groups/g/gi/
>>> gitclipse/README' and is accessible only to gitclipse shell access
>>> granted team members. It includes the admin user/passwords for the
>>> project resources that we manage. Future project resource changes
>>> should go in that file.
>>>
>>> I've added a wiki to our sourceforge page and I think I've migrated
>>> most of the things over from our class site. Updates to that
>>> documentation should probably be on the sourceforge wiki.
>>> http://gitclipse.org/wiki
>>>
>>> --
>>> Drew
>>
>> _______________________________________________
>> G22_3033_003_su08 mailing list
>> G22...@cs...
>> http://www.cs.nyu.edu/mailman/listinfo/g22_3033_003_su08
>>
> _______________________________________________
> G22_3033_003_su08 mailing list
> G22...@cs...
> http://www.cs.nyu.edu/mailman/listinfo/g22_3033_003_su08
>
|
