Hi,
I was just looking through the updated Roadmap, and noticed that this link
http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/
could be an extremely useful thing for new developers to get some sense of overview about Inkscape's structure.
I'd like to add it to the section "The Inkscape Codebase" at https://inkscape.org/en/develop/getting-started .
Is there any additional info I should include?
Regards, Maren
On Tue, Apr 28, 2015 at 06:57:37PM +0200, Maren Hachmann wrote:
Hi,
I was just looking through the updated Roadmap, and noticed that this link
http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/
could be an extremely useful thing for new developers to get some sense of overview about Inkscape's structure.
I'd like to add it to the section "The Inkscape Codebase" at https://inkscape.org/en/develop/getting-started .
Please do! In fact we were just chatting about this at lunch during the hackfest. That's a perfect place for it.
Is there any additional info I should include?
We also wondered if there were other resources or other information that would be worth adding to the getting-started page that would help newcomers. Perhaps someone that has come onboard relatively recently could review it and suggest useful information to add.
Regards, Maren
One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
I'd like to add it to the section "The Inkscape Codebase" at https://inkscape.org/en/develop/getting-started .
Please do! In fact we were just chatting about this at lunch during the hackfest. That's a perfect place for it.
- - Done.
We also wondered if there were other resources or other information that would be worth adding to the getting-started page that would help newcomers. Perhaps someone that has come onboard relatively recently could review it and suggest useful information to add.
- - I'll ask on the dev mailing list for this, then - I've got no idea who's new, the long-term contributors are easier to spot ;)
Maren
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi devs,
to make entering the project easy for new developers, we have a whole section of the website dedicated to development topics [1] We're looking for suggestions what to add / how to improve that section, especially the "Getting started" part [2]. It would be especially valuable if someone of the more recent new developers could make suggestions, as they've only just gone through the process themselves. I've just added a link to the Doxygen pages, but there's probably more which could be useful to guide our future devs ;)
Any ideas are welcome!
Regards, Maren
[1] https://inkscape.org/en/develop/ [2] https://inkscape.org/en/develop/getting-started
Am 28.04.2015 um 23:34 schrieb Bryce Harrington:
Is there any additional info I should include?
We also wondered if there were other resources or other information that would be worth adding to the getting-started page that would help newcomers. Perhaps someone that has come onboard relatively recently could review it and suggest useful information to add.
- Is there anybody specific I could ask? Seems that a general shoutout to the dev's mailing list is not a successful road.
Maren
On Thu, Apr 30, 2015 at 03:55:19PM +0200, Maren Hachmann wrote:
Am 28.04.2015 um 23:34 schrieb Bryce Harrington:
Is there any additional info I should include?
We also wondered if there were other resources or other information that would be worth adding to the getting-started page that would help newcomers. Perhaps someone that has come onboard relatively recently could review it and suggest useful information to add.
- Is there anybody specific I could ask? Seems that a general shoutout
to the dev's mailing list is not a successful road.
A trick I've used successfully in the past is to watch the IRC channel or mailing list for someone asking a lot of basic dev questions, and/or complaining about the lack of intro user documentation, and then pounce on them. :-)
Another approach with this particular document is to identify some of the questions we don't currently answer adequately, and pose them to the existing developers, and capture their answers. If you find someone who is particularly helpful at answering questions, then kindly ask them to also proofread the existing docs and identify things that are no longer current.
In general, often the problem is the people who have the time and interest in writing these docs don't know enough to be comfortable volunteering to write them. And those who do know the info, no longer need the docs, and are more interested in putting their knowledge to use. But if you can find some way to pit one off against the other, useful docs can often be emitted as a byproduct.
Bryce
participants (2)
-
Bryce Harrington -
Maren Hachmann