Roman, Thanks for getting back to me, your feedback wasn't discouraging, I just didn't really know how to proceed (so no worries).
I completely understand peoples limited time, I am in the same boat, I did not want to invest hours in writing, learning the nuances of a particular markup language, only to have a barrier thrown up at the end. This is the reason for my questions. I would be happy to format and maintain my own tutorial, as this is my first contribution of any kind, I am completely unfamiliar with the procedures, customs, and requirements for doing this on the gimp project. It sounds like the barriers that you mentioned are more technical than administrative, so that is actually pretty encouraging. I am not quite ready to checkout a module and add my own tutorial just yet, I need to read up on using Git for a collaborative project. I have used older CMS S/W (RCS, CVS) for collaborative projects, but that was a while ago. I will follow the link and do some reading. I did browse through some of the tutorials & looked at they way they were marked up. I don't think porting my tutorials into a markup language will be any problem. The part that I don't really understand yet is whether there are tags that will or won't work right. In other words, if the XHTLM is well formed and presents in a web browser is there any downstream processing that looks at or uses particular tags? e.g. some of the xhtml that I looked at used the older <b> tags for bold instead of <strong>. Both work, one is more contemporary, but what I am wondering is whether there is a reason to use the older tag format. Once I do get ready to check out the module and add my tutorial, is there any kind of an approval process, or do I just stage the changes and commit them? Thanks for the feedback & help. On Mon, Jul 1, 2013 at 12:35 AM, Roman Joost <romanof...@gimp.org> wrote: > On Fri, Jun 28, 2013 at 05:09:49PM -0700, Stephen Kiel wrote: > > Pat, > > > > Sorry for the delay in getting back to you. I would really appreciate > your > > help. While all of Roman's suggestions sounded positive and a great > idea, > > they left me wondering how I would go about accomplishing them. Having > > someone that has gone through a few of these steps or is going through > them > > would be a great help. > Sorry if I sounded discouraging. The problem for most of the GIMP people > is to take care of your contributions since there is only a limited > amount of spare time available for all of us. At the moment, the file > format you're using is incompatible at what is being used for the > homepage and/or the manual. That means, someone would need to > incorporate it. > > What you could do is, checkout the gimp-web module from: > > https://git.gnome.org/browse/gimp-web > > and try to add your tutorial. That should be something you can't export > from libre office. > > As you can see, the barrier has already risen from simply contributing > something you can write in an office application towards something where > you need to write markup and perhaps even source code. Even more, you > need to figure out how to incorporate your contributions instead of just > making them available. > > Hope that makes things more clear on where to start, but feel free to > follow your own ideas. > > Kind Regards, > -- > Roman Joost > www: http://www.romanofski.de > email: romanof...@gimp.org > -- Stephen Kiel 26602 Strafford Mission Viejo, CA 92692 *Mobile/SMS (949) 702-1993* Home (949) 367-2915 snick.k...@gmail.com http://stephenkiel.blogspot.com/
_______________________________________________ gimp-docs-list mailing list email@example.com https://mail.gnome.org/mailman/listinfo/gimp-docs-list