Re: [fossil-users] How to contribute to wiki?
On Thu, 23 May 2013 19:03:31 -0400, Richard Hipp d...@sqlite.org wrote: Do you know that you can view the formatting of these kinds of pages without checking them in? Just put the file (with a .wiki suffix) somewhere in an open checkout, then run fossil ui. Enter http://localhost:8080/doc/ckout/...; as the URL where ... is replaced by the filename. The key component in the URL is the ckout term which tells Fossil to render the files as they appear in the check-out on disk, not as they appear in the repository. According to the Formatting Rule Summary, Only a single level of enumeration list is supported by wiki. For nested lists or for enumerations that count using letters or roman numerials, use HTML, so I had to use HTML for formatting and it looks ok when viewed through http://127.0.0.1:8081/doc/ckout/mydoc.wiki. Here's the data: www.pastebin.com/raw.php?i=xA31jQXi Using Fossil through the IDE isn't as good as using a full-fledged application, but I find this good enough for using basic commands like changes, commit, add, etc. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute to wiki?
On Thu, May 23, 2013 at 11:59 AM, Gilles gilles.gana...@free.fr wrote: Hello The contents of the wiki is now part of the source code, but there's no article that explains how to contribute to it: http://fossil-scm.org/index.html/doc/trunk/www/contribute.wiki I'd like to add an article that could be useful to new users. Copy/pasting the text to this mailing list is one way. Or email the contribution to one of the many Fossil committers is another approach. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute to wiki?
On Thu, 23 May 2013 13:34:17 -0400, Richard Hipp d...@sqlite.org wrote: Copy/pasting the text to this mailing list is one way. Or email the contribution to one of the many Fossil committers is another approach. Here it is. It's a way to access Fossil from Microsoft's Express IDE, at least to use common commands: -- Integrating Fossil in the Microsoft Express 2010 IDE The Express version of Visual Studio doesn't support add-in's and plug-in's, but it's not an issue since it's still possible to use Fossil through the External Tools menu and Fossil is a CLI application anyway: 1. Tools Settings Expert Settings 2. Tools External Tools, where the items in this list map to External Tool X that we'll add to our own Fossil menu later: 1. Rename the default [New Tool 1] to eg. Commit 2. Change Command to where Fossil is located eg. c:\fossil.exe 3. Change Arguments to the required command, eg. commit -m. The user will be prompted to type the comment that Commit expects 4. Set Initial Directory to point it to the work directory where the source files are currently checked out by Fossil (eg. c:\Workspace). It's also possible to use system variables such as $(ProjectDir) instead of hard-coding the path 5. Check Prompt for arguments, since Commit requires typing a comment. Useless for commands like Changes that don't require arguments 6. Uncheck Close on Exit, so we can see what Fossil says before closing the DOS box. Note that Use Output Window will display the output in a child window within the IDE instead of opening a DOS box 7. Click on OK 3. Tools Customize Commands 1. With Menu bar = Menu Bar selected, click on Add New Menu. A new Fossil menu is displayed in the IDE's menu bar 2. Click on Modify Selection to rename it Fossil, and 3. Use the Move Down button to move it lower in the list 4. Still in Customize dialog: In the Menu bar combo, select the new Fossil menu you just created, and Click on Add Command...: From Categories, select Tools, and select External Command 1. Click on Close. It's unfortunate that the IDE doesn't say which command maps to External Command X. -- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute to wiki?
Thanks for the page, Gilles. But the formatting doesn't work so well. And I don't know how you want it to look so I can't fix it. Do you know that you can view the formatting of these kinds of pages without checking them in? Just put the file (with a .wiki suffix) somewhere in an open checkout, then run fossil ui. Enter http://localhost:8080/doc/ckout/...; as the URL where ... is replaced by the filename. The key component in the URL is the ckout term which tells Fossil to render the files as they appear in the check-out on disk, not as they appear in the repository. The markdown language is also now supported. Just use the suffix .md instead of .wiki. On Thu, May 23, 2013 at 4:15 PM, Gilles gilles.gana...@free.fr wrote: On Thu, 23 May 2013 13:34:17 -0400, Richard Hipp d...@sqlite.org wrote: Copy/pasting the text to this mailing list is one way. Or email the contribution to one of the many Fossil committers is another approach. Here it is. It's a way to access Fossil from Microsoft's Express IDE, at least to use common commands: -- Integrating Fossil in the Microsoft Express 2010 IDE The Express version of Visual Studio doesn't support add-in's and plug-in's, but it's not an issue since it's still possible to use Fossil through the External Tools menu and Fossil is a CLI application anyway: 1. Tools Settings Expert Settings 2. Tools External Tools, where the items in this list map to External Tool X that we'll add to our own Fossil menu later: 1. Rename the default [New Tool 1] to eg. Commit 2. Change Command to where Fossil is located eg. c:\fossil.exe 3. Change Arguments to the required command, eg. commit -m. The user will be prompted to type the comment that Commit expects 4. Set Initial Directory to point it to the work directory where the source files are currently checked out by Fossil (eg. c:\Workspace). It's also possible to use system variables such as $(ProjectDir) instead of hard-coding the path 5. Check Prompt for arguments, since Commit requires typing a comment. Useless for commands like Changes that don't require arguments 6. Uncheck Close on Exit, so we can see what Fossil says before closing the DOS box. Note that Use Output Window will display the output in a child window within the IDE instead of opening a DOS box 7. Click on OK 3. Tools Customize Commands 1. With Menu bar = Menu Bar selected, click on Add New Menu. A new Fossil menu is displayed in the IDE's menu bar 2. Click on Modify Selection to rename it Fossil, and 3. Use the Move Down button to move it lower in the list 4. Still in Customize dialog: In the Menu bar combo, select the new Fossil menu you just created, and Click on Add Command...: From Categories, select Tools, and select External Command 1. Click on Close. It's unfortunate that the IDE doesn't say which command maps to External Command X. -- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute?
Hi Richard, I looked at the agreement form, and it is pretty all-encompassing. Since my company integrates fossil into its product, the agreement seems to imply that all of that work would then belong to Hwaci. I am pretty sure your intent was to get the release on the contributions only, but the wording in clause 1 does not mention that. Also, do you want a hard copy of the signed form? On Tue, Feb 8, 2011 at 11:29 AM, Richard Hipp d...@sqlite.org wrote: On Sun, Feb 6, 2011 at 10:11 PM, Ivan Hamer tic...@gmail.com wrote: I would like to be able to send in some contributions, but couldn't find much information on the topic. There is a ticket on adding this info to the FAQ (http://fossil-scm.org/index.html/tktview?name=15dfbde729) Do what are the guidelines on how to contribute to fossil? Specifically, I am interested in: 1. Which branch to work on? 2. What to do with changes? (How to test? Do I create a patch? Where to send the patch?...) I am volunteering to create a wiki/faq/documentation page on this topic. I've been thinking I need to write all of this up. It has simply been crazy lately and I've had to focus on other priorities. In order to maintain clear title, I ask that all contributors sign a copyright release prior to getting check-in privilege. After receiving check-in privilege, new contributors are asked to store on branches only - at least until such time as I can evaluate their work. And, experimental changes always go on a branch. We desire to keep the trunk working and ready-to-use at all times. I need to work up checklists for coding style and design rules. I started on a testing checklist which you can see at http://www.fossil-scm.org/fossil/doc/trunk/test/release-checklist.wiki but it needs a lot of work yet. A lot of this I'll need to do since I'm the only one with the knowledge to do it. But I'd still appreciate any help and/or advice. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute?
On Thu, Feb 17, 2011 at 11:46 AM, Ivan Hamer tic...@gmail.com wrote: Hi Richard, I looked at the agreement form, and it is pretty all-encompassing. Since my company integrates fossil into its product, the agreement seems to imply that all of that work would then belong to Hwaci. I am pretty sure your intent was to get the release on the contributions only, but the wording in clause 1 does not mention that. http://www.fossil-scm.org/fossil/artifact/ffd8bab168c8dfef - Better? Also, do you want a hard copy of the signed form? On Tue, Feb 8, 2011 at 11:29 AM, Richard Hipp d...@sqlite.org wrote: On Sun, Feb 6, 2011 at 10:11 PM, Ivan Hamer tic...@gmail.com wrote: I would like to be able to send in some contributions, but couldn't find much information on the topic. There is a ticket on adding this info to the FAQ (http://fossil-scm.org/index.html/tktview?name=15dfbde729) Do what are the guidelines on how to contribute to fossil? Specifically, I am interested in: 1. Which branch to work on? 2. What to do with changes? (How to test? Do I create a patch? Where to send the patch?...) I am volunteering to create a wiki/faq/documentation page on this topic. I've been thinking I need to write all of this up. It has simply been crazy lately and I've had to focus on other priorities. In order to maintain clear title, I ask that all contributors sign a copyright release prior to getting check-in privilege. After receiving check-in privilege, new contributors are asked to store on branches only - at least until such time as I can evaluate their work. And, experimental changes always go on a branch. We desire to keep the trunk working and ready-to-use at all times. I need to work up checklists for coding style and design rules. I started on a testing checklist which you can see at http://www.fossil-scm.org/fossil/doc/trunk/test/release-checklist.wikibut it needs a lot of work yet. A lot of this I'll need to do since I'm the only one with the knowledge to do it. But I'd still appreciate any help and/or advice. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute?
On Thu, Feb 17, 2011 at 12:24 PM, Richard Hipp d...@sqlite.org wrote: On Thu, Feb 17, 2011 at 11:46 AM, Ivan Hamer tic...@gmail.com wrote: Hi Richard, I looked at the agreement form, and it is pretty all-encompassing. Since my company integrates fossil into its product, the agreement seems to imply that all of that work would then belong to Hwaci. I am pretty sure your intent was to get the release on the contributions only, but the wording in clause 1 does not mention that. http://www.fossil-scm.org/fossil/artifact/ffd8bab168c8dfef - Better? http://www.fossil-scm.org/fossil/artifact/17a59e2687887 - Or this? Also, do you want a hard copy of the signed form? On Tue, Feb 8, 2011 at 11:29 AM, Richard Hipp d...@sqlite.org wrote: On Sun, Feb 6, 2011 at 10:11 PM, Ivan Hamer tic...@gmail.com wrote: I would like to be able to send in some contributions, but couldn't find much information on the topic. There is a ticket on adding this info to the FAQ (http://fossil-scm.org/index.html/tktview?name=15dfbde729) Do what are the guidelines on how to contribute to fossil? Specifically, I am interested in: 1. Which branch to work on? 2. What to do with changes? (How to test? Do I create a patch? Where to send the patch?...) I am volunteering to create a wiki/faq/documentation page on this topic. I've been thinking I need to write all of this up. It has simply been crazy lately and I've had to focus on other priorities. In order to maintain clear title, I ask that all contributors sign a copyright release prior to getting check-in privilege. After receiving check-in privilege, new contributors are asked to store on branches only - at least until such time as I can evaluate their work. And, experimental changes always go on a branch. We desire to keep the trunk working and ready-to-use at all times. I need to work up checklists for coding style and design rules. I started on a testing checklist which you can see at http://www.fossil-scm.org/fossil/doc/trunk/test/release-checklist.wikibut it needs a lot of work yet. A lot of this I'll need to do since I'm the only one with the knowledge to do it. But I'd still appreciate any help and/or advice. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute?
Oracle's agreement addresses the contributor as either programmer or company, which is a plus. I also find it easier to follow. On Thu, Feb 17, 2011 at 2:18 PM, Richard Hipp d...@sqlite.org wrote: On Thu, Feb 17, 2011 at 1:58 PM, Chad Perrin c...@apotheon.net wrote: On Thu, Feb 17, 2011 at 12:44:26PM -0500, Richard Hipp wrote: http://www.fossil-scm.org/fossil/artifact/17a59e2687887 - Or this? I have two comments about this, at this time: This agreement applies only to any software, documentation, scripts, of other content that has been deliberately uploaded to the public distribution of Fossil found at http://www.fossil-scm.org/. A. That should probably say or other content rather than of other content. B. You might want to specify that the upload in question has been made by the Programmer, or in explicit service of the agreement, so that the agreement cannot be construed to mean that Hwaci or some third party has found some code of Programmer's unbeknownst to Programmer and uploaded it without permission or knowledge of Programmer. I am not a lawyer, and this is not legal advice. Point B here is just a change that would make *me* feel a lot better if I was in the position of considering a contribution to Fossil at this time. Another reader suggested through a side-channel that I adapt the language here: http://oss.oracle.com/oca.pdf -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute?
On Thu, Feb 17, 2011 at 5:16 PM, Ivan Hamer tic...@gmail.com wrote: Oracle's agreement addresses the contributor as either programmer or company, which is a plus. I also find it easier to follow. http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.pdf http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html On Thu, Feb 17, 2011 at 2:18 PM, Richard Hipp d...@sqlite.org wrote: On Thu, Feb 17, 2011 at 1:58 PM, Chad Perrin c...@apotheon.net wrote: On Thu, Feb 17, 2011 at 12:44:26PM -0500, Richard Hipp wrote: http://www.fossil-scm.org/fossil/artifact/17a59e2687887 - Or this? I have two comments about this, at this time: This agreement applies only to any software, documentation, scripts, of other content that has been deliberately uploaded to the public distribution of Fossil found at http://www.fossil-scm.org/. A. That should probably say or other content rather than of other content. B. You might want to specify that the upload in question has been made by the Programmer, or in explicit service of the agreement, so that the agreement cannot be construed to mean that Hwaci or some third party has found some code of Programmer's unbeknownst to Programmer and uploaded it without permission or knowledge of Programmer. I am not a lawyer, and this is not legal advice. Point B here is just a change that would make *me* feel a lot better if I was in the position of considering a contribution to Fossil at this time. Another reader suggested through a side-channel that I adapt the language here: http://oss.oracle.com/oca.pdf -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute?
On Thu, Feb 17, 2011 at 02:18:01PM -0500, Richard Hipp wrote: Another reader suggested through a side-channel that I adapt the language here: http://oss.oracle.com/oca.pdf I suggested it for two important reasons: 1) The original version from Sun is used as base by a number of legal entities. That means people are familiar with it. The only part that is generally considered somehat controversal is the patent part, which can be likely skipped in this case. 2) It is used by a big international company. That means it got the blessing from at least two legal departments (Sun and now Oracle). It also means that it has written with an international audience in mind. There are some important differences in the copyright law between the USA and e.g. continental European countries like Germany. One basic case is the question of transfer of moral rights. The FSF basically hires people for the price of 1USD in goods. Ignoring both points, this CA has the nice side aspect for being actually readable for legalese :) Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to contribute?
On Sun, Feb 6, 2011 at 10:11 PM, Ivan Hamer tic...@gmail.com wrote: I would like to be able to send in some contributions, but couldn't find much information on the topic. There is a ticket on adding this info to the FAQ (http://fossil-scm.org/index.html/tktview?name=15dfbde729) Do what are the guidelines on how to contribute to fossil? Specifically, I am interested in: 1. Which branch to work on? 2. What to do with changes? (How to test? Do I create a patch? Where to send the patch?...) I am volunteering to create a wiki/faq/documentation page on this topic. I've been thinking I need to write all of this up. It has simply been crazy lately and I've had to focus on other priorities. In order to maintain clear title, I ask that all contributors sign a copyright release prior to getting check-in privilege. After receiving check-in privilege, new contributors are asked to store on branches only - at least until such time as I can evaluate their work. And, experimental changes always go on a branch. We desire to keep the trunk working and ready-to-use at all times. I need to work up checklists for coding style and design rules. I started on a testing checklist which you can see at http://www.fossil-scm.org/fossil/doc/trunk/test/release-checklist.wiki but it needs a lot of work yet. A lot of this I'll need to do since I'm the only one with the knowledge to do it. But I'd still appreciate any help and/or advice. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
