Difference between revisions of "Help wanted"

From Inkscape Wiki
Jump to navigation Jump to search
(revoked SPAM)
m (link fix)
(3 intermediate revisions by the same user not shown)
Line 13: Line 13:
 
One of Inkscape's secrets to success is that it plans its work out, tracks tasks carefully, and works to keep all the todo lists trim and under control.  Obviously, no coding experience is needed here.  You'll need to have an eye for order, and it helps to know a bit about what's going on with Inkscape development but it isn't required.
 
One of Inkscape's secrets to success is that it plans its work out, tracks tasks carefully, and works to keep all the todo lists trim and under control.  Obviously, no coding experience is needed here.  You'll need to have an eye for order, and it helps to know a bit about what's going on with Inkscape development but it isn't required.
  
* Update the Inkscape [[Roadmap]] - Compare what's listed there with what's been recently added to the ReleaseNotes, and to recently closed Feature Requests and Bugs in the Inkscape Tracker.  Mark things done in the roadmap as appropriate (and indicate who did them).
+
* Update the Inkscape [[Roadmap]] - Compare what's listed there with what's been recently added to the [[ReleaseNotes]], and to recently closed Feature Requests and Bugs in the Inkscape Tracker.  Mark things done in the roadmap as appropriate (and indicate who did them).
* Find more tasks to add to HelpWanted
+
* Find more tasks to add to [[HelpWanted]]
* [UpdatingTrackerItems Update Tracker Items] - See that page for details.  Inkscape prides itself in keeping good track of bugs, features, and patches.  No coding ability is required.  This is an excellent way to help keep Inkscape chugging along.  In particular:
+
* [[[UpdatingTrackerItems]] Update Tracker Items] - See that page for details.  Inkscape prides itself in keeping good track of bugs, features, and patches.  No coding ability is required.  This is an excellent way to help keep Inkscape chugging along.  In particular:
 
** The low priority bugs (level 3) need reviewed prior to the 0.42 release.  Some may be fixed by now, others may be out of date or irrelevant.
 
** The low priority bugs (level 3) need reviewed prior to the 0.42 release.  Some may be fixed by now, others may be out of date or irrelevant.
 
** Try recreating the new bugs (those at level 5).  Add a comment whether you can or cannot recreate them.
 
** Try recreating the new bugs (those at level 5).  Add a comment whether you can or cannot recreate them.
 
** Search for duplicate or redundant feature requests, and mark the dupes
 
** Search for duplicate or redundant feature requests, and mark the dupes
* Go through NewFeatureProposals and pull in ideas from the Feature Request task tracker.  Add more details (be creative!) to expand and unify the ideas.  Sketch out some mockups if you so desire.  Add a comment to the Feature Request with a pointer to the wiki page that discusses it.
+
* Go through [[NewFeatureProposals]] and pull in ideas from the Feature Request task tracker.  Add more details (be creative!) to expand and unify the ideas.  Sketch out some mockups if you so desire.  Add a comment to the Feature Request with a pointer to the wiki page that discusses it.
  
 
=== Wiki Updating ===
 
=== Wiki Updating ===
Line 25: Line 25:
 
The inkscape wiki is always in need of editing and maintenance.  Inkscape depends on its community (that's you!) to keep the wiki organized and useful.
 
The inkscape wiki is always in need of editing and maintenance.  Inkscape depends on its community (that's you!) to keep the wiki organized and useful.
  
* Merge ApplicationIcons and Icons.  Also looks like these need editing and update in general
+
* Merge [[ApplicationIcons]] and Icons.  Also looks like these need editing and update in general
 
* Ensure the formatting of different wiki pages is consistent.  Make sure each page has a title, uses wiki syntax, etc.
 
* Ensure the formatting of different wiki pages is consistent.  Make sure each page has a title, uses wiki syntax, etc.
* Search for spam.  Easy, take a look at RecentChanges, review what people have posted, delete any spam.
+
* Search for spam.  Easy, take a look at [[RecentChanges]], review what people have posted, delete any spam.
* Remove useless pages.  There's a bit too many links on the main wiki page, so trimming will help reduce the clutter.  Move pages to WikiAttic or move their contents into more useful sections.
+
* Remove useless pages.  There's a bit too many links on the main wiki page, so trimming will help reduce the clutter.  Move pages to [[WikiAttic]] or move their contents into more useful sections.
** InkscapePopularity - appears abandoned and unfinished - maybe combine with another page?
+
** [[InkscapePopularity]] - appears abandoned and unfinished - maybe combine with another page?
 
** Free Desktop Graphic Suite - seems abandoned and unfinished
 
** Free Desktop Graphic Suite - seems abandoned and unfinished
** AccessibleGraphics
+
** [[AccessibleGraphics]]
** ModalInterfaces - maybe fold the basic ideas into DeveloperManual?
+
** [[ModalInterfaces]] - maybe fold the basic ideas into [[DeveloperManual]]?
** TextUsability - maybe should be moved into the InkscapeRoadmap?
+
** [[TextUsability]] - maybe should be moved into the [[InkscapeRoadmap]]?
** KeyboardShortcuts / KeyboardShortcutsToDo / KeyboardProfiles - maybe combine all of these?  Docco seems to have beem moved elsewhere
+
** [[KeyboardShortcuts]] / [[KeyboardShortcutsToDo]] / [[KeyboardProfiles]] - maybe combine all of these?  Docco seems to have beem moved elsewhere
** CPlusPlus / Pangoification - these are both done, the pages aren't really useful anymore
+
** [[CPlusPlus]] / Pangoification - these are both done, the pages aren't really useful anymore
 
* Create a nicely laid out Inkscape Developer Wiki area
 
* Create a nicely laid out Inkscape Developer Wiki area
 
** Move the items that are extremely specific to Inkscape development into it.  Don't move everything in the Developer Documentation section, though, as some of that is useful to users that are simply trying to troubleshoot problems.  Items to move:
 
** Move the items that are extremely specific to Inkscape development into it.  Don't move everything in the Developer Documentation section, though, as some of that is useful to users that are simply trying to troubleshoot problems.  Items to move:
*** DeveloperManual
+
*** [[DeveloperManual]]
*** WorkingWithCVS
+
*** [[WorkingWithCVS]]
*** HandlingPreferences
+
*** [[HandlingPreferences]]
*** AddSPObject
+
*** [[AddSPObject]]
*** ReprListeners
+
*** [[ReprListeners]]
*** InkscapeJanitors
+
*** [[InkscapeJanitors]]
 
*** Coding Style Discussion
 
*** Coding Style Discussion
*** FileTypes
+
*** [[FileTypes]]
 
*** Icons
 
*** Icons
*** InkscapeColor
+
*** [[InkscapeColor]]
*** PrintingSubsystem
+
*** [[PrintingSubsystem]]
 
*** SVG Tiny Compliance
 
*** SVG Tiny Compliance
 
*** CSS Support
 
*** CSS Support
*** TranslationInformation
+
*** [[TranslationInformation]]
*** ObjectManager
+
*** [[ObjectManager]]
*** DialogsReorganization
+
*** [[DialogsReorganization]]
 
*** Statusbar API
 
*** Statusbar API
*** SubsystemRearchitecture
+
*** [[SubsystemRearchitecture]]
*** GtkMMification
+
*** [[GtkMMification]]
*** PathRepresentaiton
+
*** [[PathRepresentaiton]]
 
*** Cairoification
 
*** Cairoification
*** ScribusInteroperability
+
*** [[ScribusInteroperability]]
 
*** Animation-(Timeline)
 
*** Animation-(Timeline)
*** NewFeatureProposals
+
*** [[NewFeatureProposals]]
*** ExtensionArchitectureProposals
+
*** [[ExtensionArchitectureProposals]]
 
** Distinguish between development ideas/proposals, plans/specs, and documentation/techniques
 
** Distinguish between development ideas/proposals, plans/specs, and documentation/techniques
 
** Add other useful links for reference documentation on topics of relevance to Inkscape development
 
** Add other useful links for reference documentation on topics of relevance to Inkscape development
*** OpenVG
+
*** [[OpenVG]]
*** OpenDocument
+
*** [[OpenDocument]]
* Flesh out the DeveloperManual - we want to expand this into something that will provide a useful reference for new (and old!) developers.   
+
* Flesh out the [[DeveloperManual]] - we want to expand this into something that will provide a useful reference for new (and old!) developers.   
** Pull in ErrorsAndWarnings, DebuggingTips, HandlingPreferences, AddSPObject, ReprListeners
+
** Pull in [[ErrorsAndWarnings]], [[DebuggingTips]], [[HandlingPreferences]], [[AddSPObject]], [[ReprListeners]]
** Look through other wiki pages for docs that really should be included in the DeveloperManual and move them there.
+
** Look through other wiki pages for docs that really should be included in the [[DeveloperManual]] and move them there.
 
** Browse through the Inkscape-devel mailing list for development tips/tricks/suggestions to add
 
** Browse through the Inkscape-devel mailing list for development tips/tricks/suggestions to add
 
** Draw some diagrams or relevant pictures to include in the manual, to help break things up
 
** Draw some diagrams or relevant pictures to include in the manual, to help break things up
 
** Create a Table of Contents
 
** Create a Table of Contents
 
** Review and update the docs to more accurately match the state of the codebase
 
** Review and update the docs to more accurately match the state of the codebase
** Skim through the inkscape codebase for comments worth adding to the DeveloperManual
+
** Skim through the inkscape codebase for comments worth adding to the [[DeveloperManual]]
  
 
=== Inkscape Promotion ===
 
=== Inkscape Promotion ===
  
Believe it or not, there are still people in the world who don't know about Inkscape.  You job is to fix this!  Here are some ideas for helping to spread the word about Inkscape:
+
Believe it or not, there are still people in the world who don't know about Inkscape.  Your job is to fix this!  Here are some ideas for helping to spread the word about Inkscape:
  
* Update InkscapeFeatures - Review recent changes to ReleaseNotes and make sure InkscapeFeatures capture all the major features we've got.
+
* Update [[InkscapeFeatures]] - Review recent changes to [[ReleaseNotes]] and make sure [[InkscapeFeatures]] capture all the major features we've got.
 
* Contact magazine publishers and ask that they include Inkscape coverage and/or copies of Inkscape in their magazine CD's
 
* Contact magazine publishers and ask that they include Inkscape coverage and/or copies of Inkscape in their magazine CD's
  
Line 90: Line 90:
 
* Join the Inkscape Manual team.  This aims to compile a complete reference, so if writing Wikipedia articles appeals to you, you'll love this!
 
* Join the Inkscape Manual team.  This aims to compile a complete reference, so if writing Wikipedia articles appeals to you, you'll love this!
 
* Write more content for the website or wiki
 
* Write more content for the website or wiki
* Get articles published about Inkscape on FootNotes, DeviantArt, FreshMeat, or other community sites
+
* Get articles published about Inkscape on [[FootNotes]], [[DeviantArt]], [[FreshMeat]], or other community sites
 +
 
 +
=== Making Screenshots ===
 +
 
 +
For a user, screenshots are perhaps the most important resource at inkscape.org. It's what most people look at first: they want pretty pictures.
 +
 
 +
Please see the [[MakingScreenshots]] page for fuller explanation of this topic and instructions on how to make screenshots and submit them to the [http://inkscape.org/screenshots/index.php gallery].
  
 
=== Inkscape Janitors ===
 
=== Inkscape Janitors ===
  
If you can code (even if you're new to coding), check out InkscapeJanitors for specific coding requests.  Code it up, create a patch, and upload it to the patch tracker.  Easy!
+
If you can code (even if you're new to coding), check out [[InkscapeJanitors]] for specific coding requests.  Code it up, create a patch, and upload it to the patch tracker.  Easy!

Revision as of 02:33, 22 January 2006

Help Wanted

This page lists easy, entry-level type tasks where help is needed. These tasks focus on non-coding, or light-coding activities that are desperately needed right now.

If you complete one of these tasks, please mark it (DONE) with your name (so we know who to give thanks to!) If you discover other tasks that you think others could do, please list them here.

Inkscape Planning

One of Inkscape's secrets to success is that it plans its work out, tracks tasks carefully, and works to keep all the todo lists trim and under control. Obviously, no coding experience is needed here. You'll need to have an eye for order, and it helps to know a bit about what's going on with Inkscape development but it isn't required.

  • Update the Inkscape Roadmap - Compare what's listed there with what's been recently added to the ReleaseNotes, and to recently closed Feature Requests and Bugs in the Inkscape Tracker. Mark things done in the roadmap as appropriate (and indicate who did them).
  • Find more tasks to add to HelpWanted
  • [[[UpdatingTrackerItems]] Update Tracker Items] - See that page for details. Inkscape prides itself in keeping good track of bugs, features, and patches. No coding ability is required. This is an excellent way to help keep Inkscape chugging along. In particular:
    • The low priority bugs (level 3) need reviewed prior to the 0.42 release. Some may be fixed by now, others may be out of date or irrelevant.
    • Try recreating the new bugs (those at level 5). Add a comment whether you can or cannot recreate them.
    • Search for duplicate or redundant feature requests, and mark the dupes
  • Go through NewFeatureProposals and pull in ideas from the Feature Request task tracker. Add more details (be creative!) to expand and unify the ideas. Sketch out some mockups if you so desire. Add a comment to the Feature Request with a pointer to the wiki page that discusses it.

Wiki Updating

The inkscape wiki is always in need of editing and maintenance. Inkscape depends on its community (that's you!) to keep the wiki organized and useful.

Inkscape Promotion

Believe it or not, there are still people in the world who don't know about Inkscape. Your job is to fix this! Here are some ideas for helping to spread the word about Inkscape:

  • Update InkscapeFeatures - Review recent changes to ReleaseNotes and make sure InkscapeFeatures capture all the major features we've got.
  • Contact magazine publishers and ask that they include Inkscape coverage and/or copies of Inkscape in their magazine CD's

Inkscape Documentation

Inkscape users love having new tutorials, guides, and references.

  • Help author, edit, translate, and review tutorials
  • Join the Inkscape Manual team. This aims to compile a complete reference, so if writing Wikipedia articles appeals to you, you'll love this!
  • Write more content for the website or wiki
  • Get articles published about Inkscape on FootNotes, DeviantArt, FreshMeat, or other community sites

Making Screenshots

For a user, screenshots are perhaps the most important resource at inkscape.org. It's what most people look at first: they want pretty pictures.

Please see the MakingScreenshots page for fuller explanation of this topic and instructions on how to make screenshots and submit them to the gallery.

Inkscape Janitors

If you can code (even if you're new to coding), check out InkscapeJanitors for specific coding requests. Code it up, create a patch, and upload it to the patch tracker. Easy!