Inkscape Website: Translation Instructions
Hey Devs and Users,
I've updated the wiki explaining the new Inkscape website's translation instructions. New translations have accidentally overwritten the English content in some places (especially the front page) so to avoid this I've put together a brief explanation of why the front page is hard to edit.
http://wiki.inkscape.org/wiki/index.php/WebSite#Translations
Please do copy plugins into your local language instead of editing the English versions. All editors are reminded that each language can have different plugins for the same content-location if they wish.
Website: http://staging.inkscape.org
If you don't have an account and would like to help get content ready, login and send me an email so I can enable staff privileges for you and have you editing the CMS.
Happy Editing, Martin Owens
Sorry about the http:500 for the past day, I did an update to the software and didn't have access to the logs to fix it until today.
http://staging.inkscape.org is back online and waiting for your contributions. The news section is now language aware and will display localised news if available. Let me know if you can't access the news admin interface if you need to translate a new story for your locale.
Best Regards, Martin Owens
On Tue, 2013-07-16 at 20:01 -0400, Martin Owens wrote:
Hey Devs and Users,
I've updated the wiki explaining the new Inkscape website's translation instructions. New translations have accidentally overwritten the English content in some places (especially the front page) so to avoid this I've put together a brief explanation of why the front page is hard to edit.
http://wiki.inkscape.org/wiki/index.php/WebSite#Translations
Please do copy plugins into your local language instead of editing the English versions. All editors are reminded that each language can have different plugins for the same content-location if they wish.
Website: http://staging.inkscape.org
If you don't have an account and would like to help get content ready, login and send me an email so I can enable staff privileges for you and have you editing the CMS.
Happy Editing, Martin Owens
Hey Devs,
http://staging.inkscape.org/en/develop/getting-started/
This page needs a valiant volunteer to author it. I believe the idea to is to combine the bzr, commit, merge process and structural overview from the wiki into this page in a nice friendly way with clear links to the developer communication channels.
Who could I convince to help write this page?
Gracious Regards, Martin
On Tue, 2013-07-16 at 20:01 -0400, Martin Owens wrote:
Hey Devs and Users,
I've updated the wiki explaining the new Inkscape website's translation instructions. New translations have accidentally overwritten the English content in some places (especially the front page) so to avoid this I've put together a brief explanation of why the front page is hard to edit.
http://wiki.inkscape.org/wiki/index.php/WebSite#Translations
Please do copy plugins into your local language instead of editing the English versions. All editors are reminded that each language can have different plugins for the same content-location if they wish.
Website: http://staging.inkscape.org
If you don't have an account and would like to help get content ready, login and send me an email so I can enable staff privileges for you and have you editing the CMS.
Happy Editing, Martin Owens
Martin,
I will help on this page, and any other pages, and items you need help with.
So I formally volunteer if that is a help.
Regards, Leo Jackson
________________________________ From: Martin Owens <doctormo@...400...> To: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Thursday, July 18, 2013 11:49 AM Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
Hey Devs,
http://staging.inkscape.org/en/develop/getting-started/
This page needs a valiant volunteer to author it. I believe the idea to is to combine the bzr, commit, merge process and structural overview from the wiki into this page in a nice friendly way with clear links to the developer communication channels.
Who could I convince to help write this page?
Gracious Regards, Martin
On Tue, 2013-07-16 at 20:01 -0400, Martin Owens wrote:
Hey Devs and Users,
I've updated the wiki explaining the new Inkscape website's translation instructions. New translations have accidentally overwritten the English content in some places (especially the front page) so to avoid this I've put together a brief explanation of why the front page is hard to edit.
http://wiki.inkscape.org/wiki/index.php/WebSite#Translations
Please do copy plugins into your local language instead of editing the English versions. All editors are reminded that each language can have different plugins for the same content-location if they wish.
Website: http://staging.inkscape.org
If you don't have an account and would like to help get content ready, login and send me an email so I can enable staff privileges for you and have you editing the CMS.
Happy Editing, Martin Owens
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Sorry, off-topic: the English flag is not very recognizable and I think should be replaced with the UK flag.
Cheers, Johan
On 17-7-2013 2:01, Martin Owens wrote:
Hey Devs and Users,
I've updated the wiki explaining the new Inkscape website's translation instructions. New translations have accidentally overwritten the English content in some places (especially the front page) so to avoid this I've put together a brief explanation of why the front page is hard to edit.
http://wiki.inkscape.org/wiki/index.php/WebSite#Translations
Please do copy plugins into your local language instead of editing the English versions. All editors are reminded that each language can have different plugins for the same content-location if they wish.
Website: http://staging.inkscape.org
If you don't have an account and would like to help get content ready, login and send me an email so I can enable staff privileges for you and have you editing the CMS.
Happy Editing, Martin Owens
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Leo,
Thank you so much! Happy to have your help.
Johan Engelen: The English flag for English, But the UK flag could stand for English or Welsh and those are just the official languages of the UK.
Martin,
On Thu, 2013-07-18 at 09:23 -0700, Leo Jackson wrote:
Martin,
I will help on this page, and any other pages, and items you need help with.
So I formally volunteer if that is a help.
Hello Martin,
How about this for a rough outline?
1. Getting the source code. 1.1 Creating a Launchpad Account etc. 1.2 Installing Bazaar locally
2. Building Inkscape 2.1 List of Dependencies 2.2 Basic Building 2.2.1 ccache, out of source builds etc.
3. Basic orgranisation of files in the src dir 3.1 i.e. where to look for things etc. directory organisation 3.2 grepping for interesting things
4. Basic developer workflow 4.1 make change, save recompile (for trivial patches) 4.2 Creating/applying diffs
5. Developer workflow 5.1 Bazaar (VCS) Basics 5.2 save, commit, recompile, test, push workflow 5.3 merging, branching, reverting
6. Inkscape Development 6.1 Programming Style 6.2 Things to do/(not do) 6.3 Links to C++/Gtk etc. references and tutorials
7. Collaboration 7.1 Using Launchpad effectively: 7.1.1 bugtracker etc 7.2 Using the Jabber chatroom, #inkscape on IRC, ML
I'm interested in helping write this. We really need all this information in one page. If people agree on the general outline, it will make things far easier for people who want to write. e.g. people can work on different areas, etc.
Samuel
On Thu, Jul 18, 2013 at 9:53 PM, Leo Jackson <lajjr@...36...> wrote:
Martin,
I will help on this page, and any other pages, and items you need help with.
So I formally volunteer if that is a help.
Regards, Leo Jackson ________________________________ From: Martin Owens <doctormo@...400...> To: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Thursday, July 18, 2013 11:49 AM Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
Hey Devs,
http://staging.inkscape.org/en/develop/getting-started/
This page needs a valiant volunteer to author it. I believe the idea to is to combine the bzr, commit, merge process and structural overview from the wiki into this page in a nice friendly way with clear links to the developer communication channels.
Who could I convince to help write this page?
Gracious Regards, Martin
On Tue, 2013-07-16 at 20:01 -0400, Martin Owens wrote:
Hey Devs and Users,
I've updated the wiki explaining the new Inkscape website's translation instructions. New translations have accidentally overwritten the English content in some places (especially the front page) so to avoid this I've put together a brief explanation of why the front page is hard to edit.
http://wiki.inkscape.org/wiki/index.php/WebSite#Translations
Please do copy plugins into your local language instead of editing the English versions. All editors are reminded that each language can have different plugins for the same content-location if they wish.
Website: http://staging.inkscape.org
If you don't have an account and would like to help get content ready, login and send me an email so I can enable staff privileges for you and have you editing the CMS.
Happy Editing, Martin Owens
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 18-7-2013 19:50, Martin Owens wrote:
Johan Engelen: The English flag for English, But the UK flag could stand for English or Welsh and those are just the official languages of the UK.
Having a country flag next to a language does not make sense, so we cannot really reason about this like that. I think it's better to remove the flags, unless the intention is to make country-specific content. If you want to preserve the icons, they at least should be clear. The (not so well-known) English flag is confusing and should be replaced with a more recognizable indication of the English language.
Related small thing: it should be 日本語 (the language) instead of 日本 (the country).
Ciao, Johan
On Thu, 2013-07-18 at 23:24 +0530, Samuel Chase wrote:
I'm interested in helping write this. We really need all this information in one page. If people agree on the general outline, it will make things far easier for people who want to write. e.g. people can work on different areas, etc.
That looks good, I think we should focus on Linux development for now and have a page later for Mac/Windows compiling if that makes sense. So we don't end up with lots of 'if this platform then...' in the developers documentation.
Thoughts?
Martin,
Hi Martin,
Possibly silly question: So, how/where do I start writing this tutorial?
Samuel
On Thu, Jul 18, 2013 at 11:43 PM, Martin Owens <doctormo@...400...> wrote:
On Thu, 2013-07-18 at 23:24 +0530, Samuel Chase wrote:
I'm interested in helping write this. We really need all this information in one page. If people agree on the general outline, it will make things far easier for people who want to write. e.g. people can work on different areas, etc.
That looks good, I think we should focus on Linux development for now and have a page later for Mac/Windows compiling if that makes sense. So we don't end up with lots of 'if this platform then...' in the developers documentation.
Thoughts?
Martin,
We can explain the simplest build instructions (e.g. say debian Linux) and then link to detailed instructions for other platforms.
On Thu, Jul 18, 2013 at 11:46 PM, Samuel Chase <samebchase@...400...> wrote:
Hi Martin,
Possibly silly question: So, how/where do I start writing this tutorial?
Samuel
On Thu, Jul 18, 2013 at 11:43 PM, Martin Owens <doctormo@...400...> wrote:
On Thu, 2013-07-18 at 23:24 +0530, Samuel Chase wrote:
I'm interested in helping write this. We really need all this information in one page. If people agree on the general outline, it will make things far easier for people who want to write. e.g. people can work on different areas, etc.
That looks good, I think we should focus on Linux development for now and have a page later for Mac/Windows compiling if that makes sense. So we don't end up with lots of 'if this platform then...' in the developers documentation.
Thoughts?
Martin,
2013/7/18 Martin Owens <doctormo@...400...>:
Hey Devs,
http://staging.inkscape.org/en/develop/getting-started/
This page needs a valiant volunteer to author it. I believe the idea to is to combine the bzr, commit, merge process and structural overview from the wiki into this page in a nice friendly way with clear links to the developer communication channels.
Who could I convince to help write this page?
I can help with this too.
This should not be a giant dump of information in the style of wiki pages. It should contain steps which a new developer should take to start hacking, something like a walkthrough, and not be longer that 2-3 screens. Detailed information (e.g. compilation instructions, devlibs information, and so on) should go on separate pages or be linked to the wiki.
Regards, Krzysztof
Martin,
No problem getting the source from bzr branch now then starting on it.
Also anything else just give a email any time.
Is there a task list or something Ian Caldwell had a doc at one time. Also the bugs can be a list, but not a todo list. Regards, Leo Jackson
________________________________ From: Martin Owens <doctormo@...400...> To: Leo Jackson <lajjr@...36...> Cc: "Inkscape-devel@lists.sourceforge.net" <Inkscape-devel@...2164...e.net> Sent: Thursday, July 18, 2013 1:50 PM Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
Leo,
Thank you so much! Happy to have your help.
Johan Engelen: The English flag for English, But the UK flag could stand for English or Welsh and those are just the official languages of the UK.
Martin,
On Thu, 2013-07-18 at 09:23 -0700, Leo Jackson wrote:
Martin,
I will help on this page, and any other pages, and items you need help with.
So I formally volunteer if that is a help.
Looks like we have 3 people to help write this page:
Leo Jackson, Samuel Chase and Krzysztof, can you all work together to divide up the work? I'm happy to have new pages made to accomindate the information spread.
Instruction for website work: http://wiki.inkscape.org/wiki/index.php/WebSite#Website_Development
Website to get started writing content on: http://staging.inkscape.org/
Martin,
On Thu, 2013-07-18 at 22:45 +0200, Krzysztof Kosiński wrote:
I can help with this too.
Hello Martin,
Yes, but we haven't decided how we're gonna structure this. Once a basic outline is approved, we can start writing, otherwise, we might end up duplicating the effort.
Please add me to the Editors group so that I can edit online.
Samuel
On Fri, Jul 19, 2013 at 2:24 AM, Martin Owens <doctormo@...400...> wrote:
Looks like we have 3 people to help write this page:
Leo Jackson, Samuel Chase and Krzysztof, can you all work together to divide up the work? I'm happy to have new pages made to accomindate the information spread.
Instruction for website work: http://wiki.inkscape.org/wiki/index.php/WebSite#Website_Development
Website to get started writing content on: http://staging.inkscape.org/
Martin,
On Thu, 2013-07-18 at 22:45 +0200, Krzysztof Kosiński wrote:
I can help with this too.
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Johan,
Thank You and Johan is correct, Martin would like me to change this.
under Japan 日本 to 日本語 ?
Regards, Leo Jackson
________________________________ From: Johan Engelen <jbc.engelen@...2592...> To: inkscape-devel@lists.sourceforge.net Sent: Thursday, July 18, 2013 2:09 PM Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
On 18-7-2013 19:50, Martin Owens wrote:
Johan Engelen: The English flag for English, But the UK flag could stand for English or Welsh and those are just the official languages of the UK.
Having a country flag next to a language does not make sense, so we cannot really reason about this like that. I think it's better to remove the flags, unless the intention is to make country-specific content. If you want to preserve the icons, they at least should be clear. The (not so well-known) English flag is confusing and should be replaced with a more recognizable indication of the English language.
Related small thing: it should be 日本語 (the language) instead of 日本 (the country).
Ciao, Johan
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, 2013-07-18 at 16:15 -0700, Leo Jackson wrote:
Martin would like me to change this.
I've updated it already in the code, but we're waiting on an upgrade from django 1.3.3 to 1.5 which I'm going to apply sometime soon.
Martin,
2013/7/18 Martin Owens <doctormo@...400...>:
Johan Engelen: The English flag for English, But the UK flag could stand for English or Welsh and those are just the official languages of the UK.
Strictly speaking that's true, but it doesn't change the fact that the UK flag means English to 99% of people, and that the English flag is not widely known outside of UK.
As a sort of compromise, we could use this combination of UK and US flags. I saw it used on a number of websites to identify the English language, and it's also the first Google image search result for "english language flag". http://commons.wikimedia.org/wiki/File:English_language.svg
Regards, Krzysztof
Martin,
"Please add me to the Editors group so that I can edit online.
Samuel"
Does Samuel mean on the Staging site?? If so I believe I may need editor permissions as well please.
Also the staging site (http://staging.inkscape.org/en/) show an error page at the moment.
Regards, Leo Jackson
________________________________ From: Samuel Chase <samebchase@...400...> To: Martin Owens <doctormo@...400...> Cc: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Thursday, July 18, 2013 5:04 PM Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
Hello Martin,
Yes, but we haven't decided how we're gonna structure this. Once a basic outline is approved, we can start writing, otherwise, we might end up duplicating the effort.
Please add me to the Editors group so that I can edit online.
Samuel
On Fri, Jul 19, 2013 at 2:24 AM, Martin Owens <doctormo@...400...> wrote:
Looks like we have 3 people to help write this page:
Leo Jackson, Samuel Chase and Krzysztof, can you all work together to divide up the work? I'm happy to have new pages made to accomindate the information spread.
Instruction for website work: http://wiki.inkscape.org/wiki/index.php/WebSite#Website_Development
Website to get started writing content on: http://staging.inkscape.org/
Martin,
On Thu, 2013-07-18 at 22:45 +0200, Krzysztof Kosiński wrote:
I can help with this too.
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I'm gonna start writing here: https://code.launchpad.net/~samebchase/+junk/getting-started-tutorial
@Leo, Krzysztof: I think it will be far more pleasant to write in a text-editor and then paste it into online-edit-text-box-thingy. That is unusable, except for the most trivial of edits. This way we can collaborate better.
@Leo: do you use lajjr or lajjr3 as your username on LP?
I've just made one initial commit with the existing content so far. I'm also considering writing in Markdown and then using something like say, pandoc to convert it to the html.
Questions/Comments etc. ?
Samuel
On Fri, Jul 19, 2013 at 2:25 PM, Leo Jackson <lajjr@...36...> wrote:
Martin,
"Please add me to the Editors group so that I can edit online.
Samuel"
Does Samuel mean on the Staging site?? If so I believe I may need editor permissions as well please.
Also the staging site (http://staging.inkscape.org/en/) show an error page at the moment.
Regards, Leo Jackson ________________________________ From: Samuel Chase <samebchase@...400...> To: Martin Owens <doctormo@...400...> Cc: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Thursday, July 18, 2013 5:04 PM
Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
Hello Martin,
Yes, but we haven't decided how we're gonna structure this. Once a basic outline is approved, we can start writing, otherwise, we might end up duplicating the effort.
Please add me to the Editors group so that I can edit online.
Samuel
On Fri, Jul 19, 2013 at 2:24 AM, Martin Owens <doctormo@...400...> wrote:
Looks like we have 3 people to help write this page:
Leo Jackson, Samuel Chase and Krzysztof, can you all work together to divide up the work? I'm happy to have new pages made to accomindate the information spread.
Instruction for website work: http://wiki.inkscape.org/wiki/index.php/WebSite#Website_Development
Website to get started writing content on: http://staging.inkscape.org/
Martin,
On Thu, 2013-07-18 at 22:45 +0200, Krzysztof Kosiński wrote:
I can help with this too.
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Can someone create an Inkscape wiki account for me? I may find opportunities to edit stuff there too.
2013/7/19 Samuel Chase <samebchase@...400...>:
@Leo, Krzysztof: I think it will be far more pleasant to write in a text-editor and then paste it into online-edit-text-box-thingy. That is unusable, except for the most trivial of edits. This way we can collaborate better.
Something broke recently, because the text editor looked totally different yesterday. The admin interface pages also seem broken (e.g. like one of the CSS files was missing).
On a related note, it would be nice if the editor took up the entire screen, rather than only its top half. The bottom space, which shows through some of the website, is not really useful for anything.
Regards, Krzysztof
On Thu, Jul 18, 2013 at 11:04 PM, Johan Engelen <jbc.engelen@...2592...> wrote:
the English flag is not very recognizable and I think should be replaced with the UK flag.
Unless Inkscape is planning to specifically use British English (EN_GB) I think the US flag should be used, as that is the most widely used form of English on the internet. I don't use US english for my communication, but on the website, EN_US is more appropriate, and therefore the US flag.
This is what has been done so far: http://staging.inkscape.org/en/develop/getting-started/
What sections to add/remove, etc?
On Fri, Jul 19, 2013 at 7:40 PM, Krzysztof Kosiński <tweenk.pl@...400...> wrote:
2013/7/19 Samuel Chase <samebchase@...400...>:
@Leo, Krzysztof: I think it will be far more pleasant to write in a text-editor and then paste it into online-edit-text-box-thingy. That is unusable, except for the most trivial of edits. This way we can collaborate better.
Something broke recently, because the text editor looked totally different yesterday. The admin interface pages also seem broken (e.g. like one of the CSS files was missing).
On a related note, it would be nice if the editor took up the entire screen, rather than only its top half. The bottom space, which shows through some of the website, is not really useful for anything.
Regards, Krzysztof
@Martin,
There seems to be some issue with the online editing. When I turned Edit mode "ON" and then edited the document, I was able to see my changes.
However, as soon as I flipped Edit Mode to "OFF" the document got reverted. How do I save my changes, so that my changes are visible globally.
In any case, this: http://bazaar.launchpad.net/~samebchase/+junk/getting-started-tutorial/view/... is the current state of things.
Samuel
On Fri, Jul 19, 2013 at 8:07 PM, Samuel Chase <samebchase@...400...> wrote:
This is what has been done so far: http://staging.inkscape.org/en/develop/getting-started/
What sections to add/remove, etc?
On Fri, Jul 19, 2013 at 7:40 PM, Krzysztof Kosiński <tweenk.pl@...1063....> wrote:
2013/7/19 Samuel Chase <samebchase@...400...>:
@Leo, Krzysztof: I think it will be far more pleasant to write in a text-editor and then paste it into online-edit-text-box-thingy. That is unusable, except for the most trivial of edits. This way we can collaborate better.
Something broke recently, because the text editor looked totally different yesterday. The admin interface pages also seem broken (e.g. like one of the CSS files was missing).
On a related note, it would be nice if the editor took up the entire screen, rather than only its top half. The bottom space, which shows through some of the website, is not really useful for anything.
Regards, Krzysztof
More readable version: https://github.com/samebchase/inkscape-getting-started/blob/master/content.m...
2013/7/19 Samuel Chase <samebchase@...400...>:
This is what has been done so far: http://staging.inkscape.org/en/develop/getting-started/
What sections to add/remove, etc?
1. Change the command for getting the source from "bzr branch" to "bzr checkout". New developers should default to the SVN style workflow, as it's easier to keep up to date with trunk and submit small patches in this fashion. Branches are better for developing larger features.
2. Do not split the text with many small headings, this looks ugly and is unreadable. For instance, all h3's under the "Fetching the source code" heading are unnecessary and could be rewritten as prose.
3. Detailed compilation instructions should not be included on this page. Instead, these should be links to the relevant pages on the wiki, or there should be separate pages on developer workflow on each platform. "Getting Started" should only contain basic information, e.g. that you need to type "btool" or "./autogen.sh; ./configure; make".
4. When it comes to Bazaar usage information, Getting Started should only include instructions on how to generate a patch. For any further info the reader should be directed to our very good "Working with Bazaar" wiki page.
5. Programming style has its own page, which is fairly complete: http://staging.inkscape.org/en/develop/coding-style/ - there should be only a link.
6. The "Collaboration" section belongs under "Community", and Getting Started should only mention how developers communicate and link the the relevant pages. Remember, this is supposed to be a brief walkthrough with pointers to more information, not a giant wall of text.
Regards, Krzysztof
On Fri, 2013-07-19 at 17:55 +0200, Krzysztof Kosiński wrote:
Change the command for getting the source from "bzr branch" to "bzr checkout".
I disagree. The branch and merge workflow allows for code reviews and better tracking in launchpad. If you recommend bzr checkout and creating patches, then we're asking developers to learn the LK method rather than the launchpad process.
If the checkout/patch method must be documented, then put it up with caveats that explain that it should only be used for very small changes < ~20 lines. Otherwise the branch/merge-request method should be used.
Martin,
On 19-7-2013 19:18, Martin Owens wrote:
On Fri, 2013-07-19 at 17:55 +0200, Krzysztof Kosiński wrote:
Change the command for getting the source from "bzr branch" to "bzr checkout".
+1
[warning added after writing my mail:] Don't read the rest of the e-mail if you're not interested in reading text from an annoyed bzr user.
I disagree. The branch and merge workflow allows for code reviews and better tracking in launchpad. If you recommend bzr checkout and creating patches, then we're asking developers to learn the LK method rather than the launchpad process.
The tracking of individual commits within the final big merge commit to trunk is pretty useless imo. I don't want to read through "implement A", "better way to implement A", "small tweak to A", "deleted A, replaced with B", series of commits. I just look at the final merge commit and see what really changed, in the context of all the other final changes. So for me, bzr branch and bzr checkout provide the same quality of history in launchpad. For code review, this argument becomes stronger for me. I really would want to look at changes within the context of all the other changes; a patch file with everything seems to do that. But who am I kidding... with the switch to bzr, I lost my capability of actually applying patches anyway [*]
If the checkout/patch method must be documented, then put it up with caveats that explain that it should only be used for very small changes < ~20 lines. Otherwise the branch/merge-request method should be used.
This depends on who we target. If we target a programmer who has not used a CVS before, "bzr branch" will probably kill all enthusiasm. (quite sure it would've for me, because it actually still does so) If we target a programmer who was interested in CVS's and learned about them and has used one before, "bzr branch" seems ok. But, this person will read-up on BZR anyway and will notice that he'd better use "bzr branch" instead of the suggested "bzr checkout". Note that I have yet to find the button "accept merge request" on launchpad's website, and I blissfully forgot how to do a merge [*].
I strongly advocate the use of "bzr checkout". If you actively collaborate with others on something, only then do I see the benefit of a branch. Please keep in mind that (I believe) many of us do not work with bzr on a daily or even weekly basis. The threshold of actually getting some work done is higher with bzr than it was with svn; without "bzr checkout" I probably would have contributed nothing any more. Let's point the "getting started" folks to this escape.
ciao, Johan
[*] don't bother explaining to me how to do it through the cmdline. If it's not possible from tortoisebzr's explorer integrated UI without having to think for more than 3 seconds, I am not interested. Hope you come and join us in the 21st century sometime! ;-)
@Samuel, I use lajjr most on launchpad.net/~lajjr and the launchpad.net/~lajjr3 are mine but lajjr3 is not part of any teams. I prefer lajjr, cause it is most used and is added to Inkscape etc.
Regards, Leo Jackson
________________________________ From: Samuel Chase <samebchase@...400...> To: Leo Jackson <lajjr@...36...> Cc: "Inkscape-devel@lists.sourceforge.net" <Inkscape-devel@...2164...e.net>; Martin Owens <doctormo@...400...> Sent: Friday, July 19, 2013 7:38 AM Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
I'm gonna start writing here: https://code.launchpad.net/~samebchase/+junk/getting-started-tutorial
@Leo, Krzysztof: I think it will be far more pleasant to write in a text-editor and then paste it into online-edit-text-box-thingy. That is unusable, except for the most trivial of edits. This way we can collaborate better.
@Leo: do you use lajjr or lajjr3 as your username on LP?
I've just made one initial commit with the existing content so far. I'm also considering writing in Markdown and then using something like say, pandoc to convert it to the html.
Questions/Comments etc. ?
Samuel
On Fri, Jul 19, 2013 at 2:25 PM, Leo Jackson <lajjr@...36...> wrote:
Martin,
"Please add me to the Editors group so that I can edit online.
Samuel"
Does Samuel mean on the Staging site?? If so I believe I may need editor permissions as well please.
Also the staging site (http://staging.inkscape.org/en/) show an error page at the moment.
Regards, Leo Jackson ________________________________ From: Samuel Chase <samebchase@...400...> To: Martin Owens <doctormo@...400...> Cc: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Thursday, July 18, 2013 5:04 PM
Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
Hello Martin,
Yes, but we haven't decided how we're gonna structure this. Once a basic outline is approved, we can start writing, otherwise, we might end up duplicating the effort.
Please add me to the Editors group so that I can edit online.
Samuel
On Fri, Jul 19, 2013 at 2:24 AM, Martin Owens <doctormo@...400...> wrote:
Looks like we have 3 people to help write this page:
Leo Jackson, Samuel Chase and Krzysztof, can you all work together to divide up the work? I'm happy to have new pages made to accomindate the information spread.
Instruction for website work: http://wiki.inkscape.org/wiki/index.php/WebSite#Website_Development
Website to get started writing content on: http://staging.inkscape.org/
Martin,
On Thu, 2013-07-18 at 22:45 +0200, Krzysztof Kosiński wrote:
I can help with this too.
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hello Krzysztof,
Thanks for the suggestions.
The latest can be found here: https://github.com/samebchase/inkscape-getting-started/blob/master/content.m...
Please review this and let me know what needs to be done.
Samuel
Apropos of NULL, I've committed a starter for our website search using whoosh and haystack, you can see it here: http://staging.inkscape.org/search/ and it looks dreadful but with tweaking should allow us multi-language searching.
For the continuing saga about bzr hating, continue reading:
On Fri, 2013-07-19 at 19:54 +0200, Johan Engelen wrote:
and I blissfully forgot how to do a merge [*].
1. Merges do not show all the commits: http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/12412 2. Code review shows the entire diff (and optionally separate commits) 3. Good documentation retains enthusiasm, even for git users 4. Launchpad/Bzr is what we use, the docs should explain that workflow and give advice for git and svn users but not special commands.
bzr branch lp:inkscape <do work> bzr commit ... bzr push lp:~user/inkscape/my-awesome-branch bzr lp-submit --fixes=lp:bugnumber
All the merger has to do is: (after review of course)
bzr merge lp:~user/inkscape/my-awesome-branch bzr commit -m "Merge in something awesome" bzr push
There's `bzr send` too, which I think you might like. It sends an email of the diff to someone.
Even the reference card is in inkscape-svg: http://doc.bazaar.canonical.com/bzr.2.4/en/_static/en/bzr-en-quick-reference...
We could include it on the website and show how "what comes around, goes around" :-D
I advocate we continue to use launchpad and bzr and document the workflows applicable to that platform.
Stubbly, Martin Owens
[1] lp-submit requires the launchpad-bzr plugin, installed by default for ubuntu/debian [2] I've worked on bzr user interfaces, my research on GUIs showed pretty awful design for distributed workflows. I have some videos here for how I saw it working: http://www.ground-control.org/videos.html
One cuestion, i made a merge using launchpad website, i dont know about the comand lp-submit. Is needed the --fixes parameter? Is this a free text?
Best regards, Jabier.
El vie, 19-07-2013 a las 16:27 -0400, Martin Owens escribió:
lp-submit
On Sat, 20 Jul 2013 00:49:24 +0200 Jabiertxo Arraiza Cenoz <jabier.arraiza@...2893...> wrote:
One cuestion, i made a merge using launchpad website, i dont know about the comand lp-submit. Is needed the --fixes parameter? Is this a free text?
bzr help commit
--fixes=ARG Mark a bug as being fixed by this revision (see "bzr help bugs").
bzr help bugs
gives more info., but it's a way of identifying bugs fixed by a commit.
Cheers -Terry
Best regards, Jabier.
El vie, 19-07-2013 a las 16:27 -0400, Martin Owens escribió:
lp-submit
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
2013/7/19 Martin Owens <doctormo@...400...>:
On Fri, 2013-07-19 at 17:55 +0200, Krzysztof Kosiński wrote:
Change the command for getting the source from "bzr branch" to "bzr checkout".
I disagree. The branch and merge workflow allows for code reviews and better tracking in launchpad. If you recommend bzr checkout and creating patches, then we're asking developers to learn the LK method rather than the launchpad process.
I don't feel strongly either way. Probably there should be a mention of both methods.
PS: if there are people interested in VCS discussion, I suggest starting another thread.
Regards, Krzysztof
On Sat, 2013-07-20 at 00:49 +0200, Jabiertxo Arraiza Cenoz wrote:
One cuestion, i made a merge using launchpad website, i dont know about the comand lp-submit. Is needed the --fixes parameter? Is this a free text?
It's the bug number the same way as for the commit command: --fixes=lp:1783899 for example.
Branches can be merge requested from the webpage too.
Martin,
2013/7/19 Johan Engelen <jbc.engelen@...2592...>:
Note that I have yet to find the button "accept merge request" on launchpad's website, and I blissfully forgot how to do a merge [*].
You should try Bazaar Explorer: http://doc.bazaar.canonical.com/explorer/en/
It doesn't have a dedicated button for applying patches, but you can go to "All" and select the "patch" command from the list, then click "Insert filename" and pick the patch file. You need the bzrtools plugins for this.
Regards, Krzysztof
We're now running django 1.5, the various errors you might have seen have been the clearing up of the templates as the url tag became less lenient.
Big thanks to Krzysztof and Jabiertxo for their bug fixes. They were a big help.
Martin,
On Thu, 2013-07-18 at 19:39 -0400, Martin Owens wrote:
I've updated it already in the code, but we're waiting on an upgrade from django 1.3.3 to 1.5 which I'm going to apply sometime soon.
@Martin
What modifications should I make to: https://github.com/samebchase/inkscape-getting-started/blob/master/content.m...
Samuel
On Sat, Jul 20, 2013 at 11:16 AM, Jabiertxo Arraiza Cenoz <jabier.arraiza@...2893...> wrote:
Ok, thanks for the info. See you.
El vie, 19-07-2013 a las 19:11 -0500, Terry Brown escribió:
Cheers -Terry
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Mon, 2013-07-22 at 11:38 +0530, Samuel Chase wrote:
What modifications should I make
Link to bzr only, we can go into details there about diffs and patches. I'd also link to a page on the website rather than a wiki page. If one doesn't exist yet, then paste in the right info from the wiki into a new page for the website.
It looks good though, what do others think?
Martin,
Hello Martin,
On Mon, Jul 22, 2013 at 4:47 PM, Martin Owens <doctormo@...400...> wrote:
Link to bzr only, we can go into details there about diffs and patches.
Fixed, to remove unnecessary bzr-specific information.
I'd also link to a page on the website rather than a wiki page. If one doesn't exist yet, then paste in the right info from the wiki into a new page for the website.
Umm... Okay. The Wiki articles, though comprehensive, are in need of some editing. What about editing the wiki article itself, so that only one has to be maintained. Otherwise, we may have two diverging articles which need to be separately maintained.
On Mon, 2013-07-22 at 17:47 +0530, Samuel Chase wrote:
Umm... Okay. The Wiki articles, though comprehensive, are in need of some editing. What about editing the wiki article itself, so that only one has to be maintained. Otherwise, we may have two diverging articles which need to be separately maintained.
The wiki has been used as a spill-over for the website for a while. My understanding is that there are many pages which need to be moved from the wiki to the website. Now that we have a CMS, that process can happen. (pages shouldn't be deleted until the website is live)
Although the wiki is still very useful for drafting, scratching and documentation. So we still need it :-)
Martin,
Samuel,
+1 Looks good I agree.
Regards, Leo Jackson
________________________________ From: Martin Owens <doctormo@...400...> To: Samuel Chase <samebchase@...400...> Cc: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Monday, July 22, 2013 7:17 AM Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
On Mon, 2013-07-22 at 11:38 +0530, Samuel Chase wrote:
What modifications should I make
Link to bzr only, we can go into details there about diffs and patches. I'd also link to a page on the website rather than a wiki page. If one doesn't exist yet, then paste in the right info from the wiki into a new page for the website.
It looks good though, what do others think?
Martin,
------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
@Martin
I realised that the "Getting Started with Inkscape" tutorial on the site is an older version.
I'm having some difficulty editing the "Getting Started Page". I have tried clicking on edit mode and pasting the html from the link below.
Could you please copy-paste this: https://raw.github.com/samebchase/inkscape-getting-started/master/content.ht... ?
Thanks,
Samuel
On Mon, Jul 22, 2013 at 11:32 PM, Leo Jackson <lajjr@...36...> wrote:
Samuel,
+1 Looks good I agree.
Regards, Leo Jackson ________________________________ From: Martin Owens <doctormo@...400...> To: Samuel Chase <samebchase@...400...> Cc: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Monday, July 22, 2013 7:17 AM
Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
On Mon, 2013-07-22 at 11:38 +0530, Samuel Chase wrote:
What modifications should I make
Link to bzr only, we can go into details there about diffs and patches. I'd also link to a page on the website rather than a wiki page. If one doesn't exist yet, then paste in the right info from the wiki into a new page for the website.
It looks good though, what do others think?
Martin,
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hey Samuel,
I've done as asked: http://staging.inkscape.org/en/develop/getting-started/
I suspect you were having problems because the page didn't have a text-box added to it. You simply add a text widget into the 'slot' and then you can edit that text widget with your html.
Martin,
On Fri, 2013-08-16 at 22:48 +0530, Samuel Chase wrote:
@Martin
I realised that the "Getting Started with Inkscape" tutorial on the site is an older version.
I'm having some difficulty editing the "Getting Started Page". I have tried clicking on edit mode and pasting the html from the link below.
Could you please copy-paste this: https://raw.github.com/samebchase/inkscape-getting-started/master/content.ht... ?
Thanks,
Samuel
On Mon, Jul 22, 2013 at 11:32 PM, Leo Jackson <lajjr@...36...> wrote:
Samuel,
+1 Looks good I agree.
Regards, Leo Jackson ________________________________ From: Martin Owens <doctormo@...400...> To: Samuel Chase <samebchase@...400...> Cc: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Monday, July 22, 2013 7:17 AM
Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
On Mon, 2013-07-22 at 11:38 +0530, Samuel Chase wrote:
What modifications should I make
Link to bzr only, we can go into details there about diffs and patches. I'd also link to a page on the website rather than a wiki page. If one doesn't exist yet, then paste in the right info from the wiki into a new page for the website.
It looks good though, what do others think?
Martin,
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Samuael,
Published I hope it is OK I published for you.
Regards, Leo Jackson
________________________________ From: Samuel Chase <samebchase@...400...> To: Cc: "Inkscape-devel@lists.sourceforge.net" <Inkscape-devel@...2164...e.net> Sent: Friday, August 16, 2013 1:18 PM Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
@Martin
I realised that the "Getting Started with Inkscape" tutorial on the site is an older version.
I'm having some difficulty editing the "Getting Started Page". I have tried clicking on edit mode and pasting the html from the link below.
Could you please copy-paste this: https://raw.github.com/samebchase/inkscape-getting-started/master/content.ht... ?
Thanks,
Samuel
On Mon, Jul 22, 2013 at 11:32 PM, Leo Jackson <lajjr@...36...> wrote:
Samuel,
+1 Looks good I agree.
Regards, Leo Jackson ________________________________ From: Martin Owens <doctormo@...400...> To: Samuel Chase <samebchase@...400...> Cc: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Monday, July 22, 2013 7:17 AM
Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
On Mon, 2013-07-22 at 11:38 +0530, Samuel Chase wrote:
What modifications should I make
Link to bzr only, we can go into details there about diffs and patches. I'd also link to a page on the website rather than a wiki page. If one doesn't exist yet, then paste in the right info from the wiki into a new page for the website.
It looks good though, what do others think?
Martin,
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
@Leo
Thanks. :-)
@Martin
Are there any other things that need to be written/re-written?
On Sat, Aug 17, 2013 at 1:18 AM, Leo Jackson <lajjr@...36...> wrote:
Samuael,
Published I hope it is OK I published for you.
Regards, Leo Jackson
From: Samuel Chase <samebchase@...400...> To: Cc: "Inkscape-devel@lists.sourceforge.net" Inkscape-devel@lists.sourceforge.net Sent: Friday, August 16, 2013 1:18 PM
Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
@Martin
I realised that the "Getting Started with Inkscape" tutorial on the site is an older version.
I'm having some difficulty editing the "Getting Started Page". I have tried clicking on edit mode and pasting the html from the link below.
Could you please copy-paste this: https://raw.github.com/samebchase/inkscape-getting-started/master/content.ht... ?
Thanks,
Samuel
On Mon, Jul 22, 2013 at 11:32 PM, Leo Jackson <lajjr@...36...> wrote:
Samuel,
+1 Looks good I agree.
Regards, Leo Jackson ________________________________ From: Martin Owens <doctormo@...400...> To: Samuel Chase <samebchase@...400...> Cc: Inkscape Devel List inkscape-devel@lists.sourceforge.net Sent: Monday, July 22, 2013 7:17 AM
Subject: Re: [Inkscape-devel] Inkscape Website: Getting Started with Development
On Mon, 2013-07-22 at 11:38 +0530, Samuel Chase wrote:
What modifications should I make
Link to bzr only, we can go into details there about diffs and patches. I'd also link to a page on the website rather than a wiki page. If one doesn't exist yet, then paste in the right info from the wiki into a new page for the website.
It looks good though, what do others think?
Martin,
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clk...
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Thanks Samuel, nice work on the getting started page.
On Sat, 2013-08-17 at 15:08 +0530, Samuel Chase wrote:
Are there any other things that need to be written/re-written?
The main develop page needs to be rewritten:
http://staging.inkscape.org/en/develop/
The aim is to have it be an invitation and general description of the different kinds of development in inkscape. For example: Extension Building, Core Development, Translations etc with those linking off where needed to more specific instructions.
Martin,
@Martin
On Sat, Aug 17, 2013 at 9:14 PM, Martin Owens <doctormo@...400...> wrote:
The aim is to have it be an invitation and general description of the different kinds of development in inkscape. For example: Extension Building, Core Development, Translations etc with those linking off where needed to more specific instructions.
Can you link me to the appropriate information (i.e. raw material) that could be consolidated into one or more of these subsections? A rough outline?
What I mean to say is that I don't know how to write a tutorial on writing Inkscape extensions, but I could surely massage a few bits an pieces of information from various sources (wiki, blogs etc.) into one coherent article.
Samuel
Hey Samual,
OK I wasn't explaining this well, so I've written a basic version of what I'd like:
On Sat, 2013-08-17 at 22:54 +0530, Samuel Chase wrote:
@Martin
On Sat, Aug 17, 2013 at 9:14 PM, Martin Owens <doctormo@...400...> wrote:
The aim is to have it be an invitation and general description of the different kinds of development in inkscape. For example: Extension Building, Core Development, Translations etc with those linking off where needed to more specific instructions.
Can you link me to the appropriate information (i.e. raw material) that could be consolidated into one or more of these subsections? A rough outline?
What I mean to say is that I don't know how to write a tutorial on writing Inkscape extensions, but I could surely massage a few bits an pieces of information from various sources (wiki, blogs etc.) into one coherent article.
Samuel
Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clk... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Sorry about that last email... evolution sent the message uncompleted.
As I was saying, I've put together a basic outline of the text:
http://staging.inkscape.org/en/develop/
And what you'll notice is that none of the sections on this page tell you how to do things. It's more of an general "These are the things you could help with and here's the links to where you could find them."
Each little section could do with some little graphics to make it all friendly. And of course each of the links I've put in that just say
here< need to be created.
Does this make more sense now?
Feel free to change an of the copy, I've done my best but I'm no author.
Martin,
@Martin
I've edited it.
participants (7)
-
Jabiertxo Arraiza Cenoz -
Johan Engelen -
Krzysztof Kosiński -
Leo Jackson -
Martin Owens -
Samuel Chase -
Terry Brown