Alexis Gallagher <email@example.com> wrote on 03/10/2005 07:05:05
> I notice a lot of the subclipse documentation is a little thin. As I
> am going to be learning some of these commands for the the first time,
> and teaching them to people on my team with less of a background than
> me, it would fit into my existing responsibilities if I contributed
> new documentation myself -- as long as there's not too much overhead
> for me getting in the loop administratively. Is that easy to do? I
> suppose I should direct this to the dev list instead...
The documentation is just HTML, so it is pretty easy to contribute to. You
just need to use Subclipse to checkout the UI plugin from the subclipse3
branch. Then just use Create Patch and send the submissions to the dev@
list or enter them in the issue tracker as a patch. We would certainly
appreciate the contributions.
Also, if you didn't notice, we have also made the "Subversion Book"
available as a plugin. You should be able to install it from the same
update site as Subclipse. This adds the text of the Subversion book the
Eclipse help system, makes it searchable etc.. This is good if you want a
handy explanation of general Subversion concepts.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Fri Mar 11 00:26:06 2005