Re: [JPP-Devel] Wikispaces
Hi London, I still don't yhave any idea about. I think that probabily we should find a new solution for wiki page for at least 2 reasons: 1) to avoid spamm 2) more order for the problem 1) Jon seems to have some solution. Regarding point 2), actual OJ wiki page has become complicate (and I have my part of responsabilities) with so many pages and duplicates. Whatever is the solution we can define some rules for wiki pages. For instance, after a while all the help documentation should be transfered to PDF format; out of dated pages should be removed from wiki, etc. Anyhow we should save the possibility that everybody can contribute to the project (see Enric's job) with the easiest way (like the wiki way) --- Sunburned Surveyor [EMAIL PROTECTED] ha scritto: Stefan, You wrote: currently Eric J. does also post a lot of OSX related content.. This is good to now. Thanks Eric! Stefan wrote; not sure what the best thing is. The wiki replaced a proper website, due to the fact that nobody (I) was able to build up and maintain a real web page as it would require for our project. It is this kind of offset we have to deal with: proper webpage or the possibility for contributions by everyone without barriers I'm not sure what the best thing is either. I'm sure this is a problem that many open source projects deal with. I will say wikis tend to be very scattered. I sometimes feel like I have to really sift through the wiki on a projet to find material of benefit. Maybe this is the advantage of having a central portal through which online documentation travels. Maybe we have another user and/or programmer that would volunteer to help us in this regard? I could set up a simple HTML template. Then the volunteer would only have to add the p elements with the text content. It sounds like Jon is willing to work with us, though I don't want to be more of a burden on him than we already are! :] I will throw my own limited documentation efforts behind whatever solution the group decides to pursue. I'd like to know what Peppe thinks. The Sunburned Surveyor On Tue, Apr 22, 2008 at 2:57 PM, Jonathan Aquino [EMAIL PROTECTED] wrote: Hi Larry - A year or two ago I added a mild anti-spam measure (email me if interested), so that helps a bit, but it sounds like someone may have figured out how to work around it. If this becomes a greater issue (i.e., spamming becomes more frequent), I can look into other anti-spam measures, such as adding a captcha. Jon From: Larry Becker [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 2:23 PM To: OpenJump develop and use; Jonathan Aquino Subject: Re: [JPP-Devel] Wikispaces I think we should give Jon time to weigh in on this issue. There may be an update or setting in the wiki software that will implement some kind of anti-spam. regards, Larry On Tue, Apr 22, 2008 at 4:11 PM, Sunburned Surveyor [EMAIL PROTECTED] wrote: Stefan wrote: btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) I can delete both sites when we make a final decision. But I will try to avoid using the term openjump in future test pages. Stefan wrote: and there are adds on the right I saw that. I don't have any major objections as long as the adds aren't obnoxious. For a few dollars a month we can remove the adds. Stefan wrote: however, as I said. also Sourceforge offers a wiki (for registred project members). I'm comfortable using the SourceForge wiki site we are provided. I think Peppe may have done some work on this wiki before. I just thought I would suggest some different options. Should we give ourselves a deadline for a decision? I'm afraid if we don't do at least that we will continue to use the same old thing until it blows up... At any rate, I think you, Peppe, and I are the main wiki users. Is there another regular wiki contributor? Maybe Larry Becker? The Sunburned Surveyor On Tue, Apr 22, 2008 at 1:40 PM, Stefan Steiniger [EMAIL PROTECTED] wrote: to tech like, and there are adds on the right btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) Because in 2 weeks the problem may be that the pages with the term openjump are registered on an index and people find the empty sites when googling... however, as I said. also Sourceforge offers a wiki (for registred project members). But such a decision needs to be well thought. stefan Sunburned Surveyor wrote: I just checked out this wiki host, which I really like: http://openjump.wikispaces.com/ Only members of wikispaces can edit pages
Re: [JPP-Devel] Wikispaces
to tech like, and there are adds on the right btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) Because in 2 weeks the problem may be that the pages with the term openjump are registered on an index and people find the empty sites when googling... however, as I said. also Sourceforge offers a wiki (for registred project members). But such a decision needs to be well thought. stefan Sunburned Surveyor wrote: I just checked out this wiki host, which I really like: http://openjump.wikispaces.com/ Only members of wikispaces can edit pages, and there is a single button to click for a wiki back-up. Users of the wiki can use a WYSIWYG editor and don't need to know any markup code. Let me know what you think. The Sunburned Surveyor - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Wikispaces
I think we should give Jon time to weigh in on this issue. There may be an update or setting in the wiki software that will implement some kind of anti-spam. regards, Larry On Tue, Apr 22, 2008 at 4:11 PM, Sunburned Surveyor [EMAIL PROTECTED] wrote: Stefan wrote: btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) I can delete both sites when we make a final decision. But I will try to avoid using the term openjump in future test pages. Stefan wrote: and there are adds on the right I saw that. I don't have any major objections as long as the adds aren't obnoxious. For a few dollars a month we can remove the adds. Stefan wrote: however, as I said. also Sourceforge offers a wiki (for registred project members). I'm comfortable using the SourceForge wiki site we are provided. I think Peppe may have done some work on this wiki before. I just thought I would suggest some different options. Should we give ourselves a deadline for a decision? I'm afraid if we don't do at least that we will continue to use the same old thing until it blows up... At any rate, I think you, Peppe, and I are the main wiki users. Is there another regular wiki contributor? Maybe Larry Becker? The Sunburned Surveyor On Tue, Apr 22, 2008 at 1:40 PM, Stefan Steiniger [EMAIL PROTECTED] wrote: to tech like, and there are adds on the right btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) Because in 2 weeks the problem may be that the pages with the term openjump are registered on an index and people find the empty sites when googling... however, as I said. also Sourceforge offers a wiki (for registred project members). But such a decision needs to be well thought. stefan Sunburned Surveyor wrote: I just checked out this wiki host, which I really like: http://openjump.wikispaces.com/ Only members of wikispaces can edit pages, and there is a single button to click for a wiki back-up. Users of the wiki can use a WYSIWYG editor and don't need to know any markup code. Let me know what you think. The Sunburned Surveyor - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- http://amusingprogrammer.blogspot.com/ - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Wikispaces
currently Eric J. does also post a lot of OSX related content (have a look on the authors page: http://openjump.org/wiki/authors) But the issue is, that we actually need those authors that contribute only 2-3 times (when they discover if something does not work, or how something works). See for instance all anonymous entries. Otherwise - when it is only us 3-4 - we could simply stick to a homepage on sourceforge. (so deriving from my argumentation, the need for registration is another downside on Sourceforge, besides the embedding). not sure what the best thing is. The wiki replaced a proper website, due to the fact that nobody (I) was able to build up and maintain a real web page as it would require for our project. It is this kind of offset we have to deal with: proper webpage or the possibility for contributions by everyone without barriers ? ? ? stefan At any rate, I think you, Peppe, and I are the main wiki users. Is there another regular wiki contributor? Maybe Larry Becker? The Sunburned Surveyor On Tue, Apr 22, 2008 at 1:40 PM, Stefan Steiniger [EMAIL PROTECTED] wrote: to tech like, and there are adds on the right btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) Because in 2 weeks the problem may be that the pages with the term openjump are registered on an index and people find the empty sites when googling... however, as I said. also Sourceforge offers a wiki (for registred project members). But such a decision needs to be well thought. stefan Sunburned Surveyor wrote: I just checked out this wiki host, which I really like: http://openjump.wikispaces.com/ Only members of wikispaces can edit pages, and there is a single button to click for a wiki back-up. Users of the wiki can use a WYSIWYG editor and don't need to know any markup code. Let me know what you think. The Sunburned Surveyor - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Wikispaces
Hi Larry - A year or two ago I added a mild anti-spam measure (email me if interested), so that helps a bit, but it sounds like someone may have figured out how to work around it. If this becomes a greater issue (i.e., spamming becomes more frequent), I can look into other anti-spam measures, such as adding a captcha. Jon _ From: Larry Becker [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 2:23 PM To: OpenJump develop and use; Jonathan Aquino Subject: Re: [JPP-Devel] Wikispaces I think we should give Jon time to weigh in on this issue. There may be an update or setting in the wiki software that will implement some kind of anti-spam. regards, Larry On Tue, Apr 22, 2008 at 4:11 PM, Sunburned Surveyor [EMAIL PROTECTED] wrote: Stefan wrote: btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) I can delete both sites when we make a final decision. But I will try to avoid using the term openjump in future test pages. Stefan wrote: and there are adds on the right I saw that. I don't have any major objections as long as the adds aren't obnoxious. For a few dollars a month we can remove the adds. Stefan wrote: however, as I said. also Sourceforge offers a wiki (for registred project members). I'm comfortable using the SourceForge wiki site we are provided. I think Peppe may have done some work on this wiki before. I just thought I would suggest some different options. Should we give ourselves a deadline for a decision? I'm afraid if we don't do at least that we will continue to use the same old thing until it blows up... At any rate, I think you, Peppe, and I are the main wiki users. Is there another regular wiki contributor? Maybe Larry Becker? The Sunburned Surveyor On Tue, Apr 22, 2008 at 1:40 PM, Stefan Steiniger [EMAIL PROTECTED] wrote: to tech like, and there are adds on the right btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) Because in 2 weeks the problem may be that the pages with the term openjump are registered on an index and people find the empty sites when googling... however, as I said. also Sourceforge offers a wiki (for registred project members). But such a decision needs to be well thought. stefan Sunburned Surveyor wrote: I just checked out this wiki host, which I really like: http://openjump.wikispaces.com/ Only members of wikispaces can edit pages, and there is a single button to click for a wiki back-up. Users of the wiki can use a WYSIWYG editor and don't need to know any markup code. Let me know what you think. The Sunburned Surveyor - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao ne ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao ne ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javao ne ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel -- http://amusingprogrammer.blogspot.com/ - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
Re: [JPP-Devel] Wikispaces
Stefan, You wrote: currently Eric J. does also post a lot of OSX related content.. This is good to now. Thanks Eric! Stefan wrote; not sure what the best thing is. The wiki replaced a proper website, due to the fact that nobody (I) was able to build up and maintain a real web page as it would require for our project. It is this kind of offset we have to deal with: proper webpage or the possibility for contributions by everyone without barriers I'm not sure what the best thing is either. I'm sure this is a problem that many open source projects deal with. I will say wikis tend to be very scattered. I sometimes feel like I have to really sift through the wiki on a projet to find material of benefit. Maybe this is the advantage of having a central portal through which online documentation travels. Maybe we have another user and/or programmer that would volunteer to help us in this regard? I could set up a simple HTML template. Then the volunteer would only have to add the p elements with the text content. It sounds like Jon is willing to work with us, though I don't want to be more of a burden on him than we already are! :] I will throw my own limited documentation efforts behind whatever solution the group decides to pursue. I'd like to know what Peppe thinks. The Sunburned Surveyor On Tue, Apr 22, 2008 at 2:57 PM, Jonathan Aquino [EMAIL PROTECTED] wrote: Hi Larry - A year or two ago I added a mild anti-spam measure (email me if interested), so that helps a bit, but it sounds like someone may have figured out how to work around it. If this becomes a greater issue (i.e., spamming becomes more frequent), I can look into other anti-spam measures, such as adding a captcha. Jon From: Larry Becker [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 22, 2008 2:23 PM To: OpenJump develop and use; Jonathan Aquino Subject: Re: [JPP-Devel] Wikispaces I think we should give Jon time to weigh in on this issue. There may be an update or setting in the wiki software that will implement some kind of anti-spam. regards, Larry On Tue, Apr 22, 2008 at 4:11 PM, Sunburned Surveyor [EMAIL PROTECTED] wrote: Stefan wrote: btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) I can delete both sites when we make a final decision. But I will try to avoid using the term openjump in future test pages. Stefan wrote: and there are adds on the right I saw that. I don't have any major objections as long as the adds aren't obnoxious. For a few dollars a month we can remove the adds. Stefan wrote: however, as I said. also Sourceforge offers a wiki (for registred project members). I'm comfortable using the SourceForge wiki site we are provided. I think Peppe may have done some work on this wiki before. I just thought I would suggest some different options. Should we give ourselves a deadline for a decision? I'm afraid if we don't do at least that we will continue to use the same old thing until it blows up... At any rate, I think you, Peppe, and I are the main wiki users. Is there another regular wiki contributor? Maybe Larry Becker? The Sunburned Surveyor On Tue, Apr 22, 2008 at 1:40 PM, Stefan Steiniger [EMAIL PROTECTED] wrote: to tech like, and there are adds on the right btw.. I think you should not immediatly register for a wiki page service only for testing and put the term openjump there ;) Because in 2 weeks the problem may be that the pages with the term openjump are registered on an index and people find the empty sites when googling... however, as I said. also Sourceforge offers a wiki (for registred project members). But such a decision needs to be well thought. stefan Sunburned Surveyor wrote: I just checked out this wiki host, which I really like: http://openjump.wikispaces.com/ Only members of wikispaces can edit pages, and there is a single button to click for a wiki back-up. Users of the wiki can use a WYSIWYG editor and don't need to know any markup code. Let me know what you think. The Sunburned Surveyor - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting
Re: [JPP-Devel] Wikispaces
hello everyone, have you considered instead using a subversion/trac setup? the nice thing about this setup is that it eliminates a lot of redundancy as it relates to application documentation. for example, as bugs, feature requests, etc., are reported, those same entries can then be re- purposed as documentation. if the repo is setup correctly from the get-go, meaning end-user gui stuff like buttons, menu selections, operations, etc. are indexed in the bug/feature request menu selections, and associated with the respective classes/interfaces, then this allows non-programmers to easily report a bug or feature request to the right place. an example of what i mean is this: go to openump at sourceforge and select 'submit new bug' and look at the 'category' pull-down menu selections. in this menu the user has: interface jts misc. openjump plugin wfsplugin the above selections serve no useful purpose for the average user(or the active oj programmer), who in all likeliness will be reporting the majority of the problems/bugs. this means it serves little purpose for those who may work on correcting the problem. bug/ticket reporting should be designed for the end user, not the programmer. the association however is what is important to the programmer, and making sure that the ticket that was reported is associated with the correct page/portion/snippet of code that in fact is responsible. this means each source code document should have a plain english reference in it(commented out), or multiple references throughout the document as is needed/warranted. imo, the easiest and best way to do this is by using the gui elements, such as menu items, icon/button items, and contextual menu items as the means of reference. thus, if i was using oj, and encountered a bug, or have an idea of how something could work better(feature request), the oj repo should offer me the following when i am submitting a ticket: Submit New Ticket: pull-down menu #1: bug minor(does not work correctly) medium(works intermittently) major(does not work) feature request core plug-in spelling correction menus help operations appearance menu icon layout pull-down menu #2: vista xp os x linux pull-down menu #3: File Edit View Layer Tools Queries Spatial Query Attribute Query Simple Query Analysis Generate Warp Edit Geometry QA Edit Attributes Generalization Measure in Feet Customize Scripting Image Plugins QA Window Help in the above shortened example, lets say the user selected Bug, OS X, Tools Queries Spatial Query . upon doing so, the respective page(s) of source code that is responsible for 'Spatial Query' should associated. when the user writes a summary and submits the ticket, at that point it is immediately associated with the proper source code page(s). this way, when a programmer looks to address the issue, he need not hunt around trying to locate it's exact location. furthermore, upon ticket submission, the user, and any other user that may view the ticket, can see it's respective association/source code. of course, this means that during the setup of the initial repo, all of this association has to be done. this is something i am willing to do, but will require on you(programmers) who are familiar with the entire inner workings of oj, to help me. of course, once it's done, then thereafter it's just a matter of properly commenting any new source code pages/code snippets in existing pages. anther suggestion i will make is that once the above is completed, we take and create donation pools for any/all bug and feature requests(tickets) that are open on the site. we create a means by which users can commit 'x' amount of money towards a ticket(bug fix or feature addition). we also create a means by which oj programmers can note their best estimate of how many programming hours will be required for said ticket. for example, let's say i filed or found a previously filed ticket for a feature request that i too would like to see implemented. i then want to stimulate some community activity by putting some money where my mouth is, electing to commit $200usd towards the ticket. the ticket indicates that 4 oj programmers have determined it will take about 5 programming hours to complete, and the industry rate for respective programming work is $50usd per hour,
