[Pharo-project] HowToContribute wiki page rewrite
Hello, I took the liberty of rewriting the HowToContribute wiki page [1] with some of the information from the recent discussion in the mailing list. Please take a look at the wiki page (I have also reproduced the text below) and feel free to make corrections yourself (or post a reply to this message and I'll take care of it). Please take special care reviewing the "publish to PharoInbox" step, since I have yet to publish anything myself so I might have gotten it wrong. Best regards, VÃctor RodrÃguez. p.s. I got to watch two "Smalltalk daily" [2] screencasts while waiting for the edited page to save.. any timetable on the nifty Pier or Cmsbox Pharo project site? :-) [1] http://gforge.inria.fr/plugins/wiki/index.php?id=1299&type=g [2] http://www.cincomsmalltalk.com/blog/blogView?searchCategory=screencast First and foremost, you must be aware that '''the Pharo project only accepts code published under the MIT license'''. By publishing your code in the !SqueakSource Pharo or !PharoInbox repositories, you are agreeing to this condition. With that out of the way, here are the steps to submit your contributions: * Prepare a changeset with your changes. File it out. '''Important''': Put your Full name instead of your initials, it will help up to contact you as it is often necessary. * Load your changes into a fresh image: ** Download the latest Pharo image from [Files | http://gforge.inria.fr/frs/?group_id=1299]. ** Launch the fresh image and load the latest updates by clicking on the ''load code updates'' button on the left flap. ** Importat: Save the image at this point, so that you don't need to reload the updates when you test your changes. ** File in your changeset. * Create a SLICE package in your package cache: ** Open the Monticello browser. You should see one or more packages marked as modified (they have an asterisk before their name). ** Select your package-cache repository on the right hand pane. ** Create the new package (click on the ''+Package'' button). Name it SLICE-nameofchange, (e.g. SLICE-remove-isMorphic). ** Make all the modified packages (the ones with asterisks before their names) required by your SLICE package. To do this, right click on the SLICE package in the left pane and select ''add required package'', then select the package from the next menu. Repeat for all modified packages. ** Save the SLICE package (click on the ''Save'' button). An mcz package will be saved in your cache for the SLICE package and all the modified packages. You will be prompted for a log message for each one of them, type a useful comment for the first package, copy it and paste it on the others. ** To prepare for the next step, quit the image without saving. * Test your packages in the clean image. ** Relaunch the clean Pharo image. If you didn't save the image after loading the updates, load the updates (I told you it was important!). ** Open the Monticello browser. ** Open your package-cache repository (select the package-cache in the right pane, click on the ''Open'' button). ** Load your SLICE package. If it loads without errors, you are ready for the next step. If there are errors, try again, or ask for help in the mailing list. * Publish the SLICE package to !PharoInbox !SqueakSource repository. ** In the Monticello browser add the !PharoInbox repository. Make sure the SLICE package is selected in the left pane, then click on the ''+Repository''. Select ''HTTP'' from the menu, then make sure that the location reads ''http://www.squeaksource.com/PharoInbox''. ** Finally, click on ''Save''. * Announce your contribution. ** You might need to add an entry to the [tracker | http://gforge.inria.fr/tracker/?group_id=1299], to MantisBugsHarvested in the wiki, etc. ** Send a email to the mailing list. Congratulations, the world is one step closer to being a better place! We greately appreciate your effort. In case of problems, you can send a changeset to the mailing list, but please only do this as a last resort.
I like it. Someone put your version online already. thanks for this, Alexandre On 4 Jun 2008, at 05:51, Victor Rodriguez wrote:
Hello,
I took the liberty of rewriting the HowToContribute wiki page [1] with some of the information from the recent discussion in the mailing list.
Please take a look at the wiki page (I have also reproduced the text below) and feel free to make corrections yourself (or post a reply to this message and I'll take care of it).
Please take special care reviewing the "publish to PharoInbox" step, since I have yet to publish anything myself so I might have gotten it wrong.
Best regards,
VÃctor RodrÃguez.
p.s. I got to watch two "Smalltalk daily" [2] screencasts while waiting for the edited page to save.. any timetable on the nifty Pier or Cmsbox Pharo project site? :-)
[1] http://gforge.inria.fr/plugins/wiki/index.php?id=1299&type=g [2] http://www.cincomsmalltalk.com/blog/blogView?searchCategory=screencast
First and foremost, you must be aware that '''the Pharo project only accepts code published under the MIT license'''. By publishing your code in the !SqueakSource Pharo or !PharoInbox repositories, you are agreeing to this condition.
With that out of the way, here are the steps to submit your contributions:
* Prepare a changeset with your changes. File it out. '''Important''': Put your Full name instead of your initials, it will help up to contact you as it is often necessary.
* Load your changes into a fresh image:
** Download the latest Pharo image from [Files | http://gforge.inria.fr/frs/?group_id=1299].
** Launch the fresh image and load the latest updates by clicking on the ''load code updates'' button on the left flap.
** Importat: Save the image at this point, so that you don't need to reload the updates when you test your changes.
** File in your changeset.
* Create a SLICE package in your package cache:
** Open the Monticello browser. You should see one or more packages marked as modified (they have an asterisk before their name).
** Select your package-cache repository on the right hand pane.
** Create the new package (click on the ''+Package'' button). Name it SLICE-nameofchange, (e.g. SLICE-remove-isMorphic).
** Make all the modified packages (the ones with asterisks before their names) required by your SLICE package. To do this, right click on the SLICE package in the left pane and select ''add required package'', then select the package from the next menu. Repeat for all modified packages.
** Save the SLICE package (click on the ''Save'' button). An mcz package will be saved in your cache for the SLICE package and all the modified packages. You will be prompted for a log message for each one of them, type a useful comment for the first package, copy it and paste it on the others.
** To prepare for the next step, quit the image without saving.
* Test your packages in the clean image.
** Relaunch the clean Pharo image. If you didn't save the image after loading the updates, load the updates (I told you it was important!).
** Open the Monticello browser.
** Open your package-cache repository (select the package-cache in the right pane, click on the ''Open'' button).
** Load your SLICE package. If it loads without errors, you are ready for the next step. If there are errors, try again, or ask for help in the mailing list.
* Publish the SLICE package to !PharoInbox !SqueakSource repository.
** In the Monticello browser add the !PharoInbox repository. Make sure the SLICE package is selected in the left pane, then click on the ''+Repository''. Select ''HTTP'' from the menu, then make sure that the location reads ''http://www.squeaksource.com/PharoInbox''.
** Finally, click on ''Save''.
* Announce your contribution.
** You might need to add an entry to the [tracker | http://gforge.inria.fr/tracker/?group_id=1299], to MantisBugsHarvested in the wiki, etc.
** Send a email to the mailing list.
Congratulations, the world is one step closer to being a better place!
We greately appreciate your effort.
In case of problems, you can send a changeset to the mailing list, but please only do this as a last resort.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Thank you Victor for your contributions. I think you have to create a SLICE package only if your modifications impact severals packages. 2008/6/4 Victor Rodriguez <victorr@gmail.com>:
Hello,
I took the liberty of rewriting the HowToContribute wiki page [1] with some of the information from the recent discussion in the mailing list.
Please take a look at the wiki page (I have also reproduced the text below) and feel free to make corrections yourself (or post a reply to this message and I'll take care of it).
Please take special care reviewing the "publish to PharoInbox" step, since I have yet to publish anything myself so I might have gotten it wrong.
Best regards,
VÃctor RodrÃguez.
p.s. I got to watch two "Smalltalk daily" [2] screencasts while waiting for the edited page to save.. any timetable on the nifty Pier or Cmsbox Pharo project site? :-)
[1] http://gforge.inria.fr/plugins/wiki/index.php?id=1299&type=g [2] http://www.cincomsmalltalk.com/blog/blogView?searchCategory=screencast
First and foremost, you must be aware that '''the Pharo project only accepts code published under the MIT license'''. By publishing your code in the !SqueakSource Pharo or !PharoInbox repositories, you are agreeing to this condition.
With that out of the way, here are the steps to submit your contributions:
* Prepare a changeset with your changes. File it out. '''Important''': Put your Full name instead of your initials, it will help up to contact you as it is often necessary.
* Load your changes into a fresh image:
** Download the latest Pharo image from [Files | http://gforge.inria.fr/frs/?group_id=1299].
** Launch the fresh image and load the latest updates by clicking on the ''load code updates'' button on the left flap.
** Importat: Save the image at this point, so that you don't need to reload the updates when you test your changes.
** File in your changeset.
* Create a SLICE package in your package cache:
** Open the Monticello browser. You should see one or more packages marked as modified (they have an asterisk before their name).
** Select your package-cache repository on the right hand pane.
** Create the new package (click on the ''+Package'' button). Name it SLICE-nameofchange, (e.g. SLICE-remove-isMorphic).
** Make all the modified packages (the ones with asterisks before their names) required by your SLICE package. To do this, right click on the SLICE package in the left pane and select ''add required package'', then select the package from the next menu. Repeat for all modified packages.
** Save the SLICE package (click on the ''Save'' button). An mcz package will be saved in your cache for the SLICE package and all the modified packages. You will be prompted for a log message for each one of them, type a useful comment for the first package, copy it and paste it on the others.
** To prepare for the next step, quit the image without saving.
* Test your packages in the clean image.
** Relaunch the clean Pharo image. If you didn't save the image after loading the updates, load the updates (I told you it was important!).
** Open the Monticello browser.
** Open your package-cache repository (select the package-cache in the right pane, click on the ''Open'' button).
** Load your SLICE package. If it loads without errors, you are ready for the next step. If there are errors, try again, or ask for help in the mailing list.
* Publish the SLICE package to !PharoInbox !SqueakSource repository.
** In the Monticello browser add the !PharoInbox repository. Make sure the SLICE package is selected in the left pane, then click on the ''+Repository''. Select ''HTTP'' from the menu, then make sure that the location reads ''http://www.squeaksource.com/PharoInbox''.
** Finally, click on ''Save''.
* Announce your contribution.
** You might need to add an entry to the [tracker | http://gforge.inria.fr/tracker/?group_id=1299], to MantisBugsHarvested in the wiki, etc.
** Send a email to the mailing list.
Congratulations, the world is one step closer to being a better place!
We greately appreciate your effort.
In case of problems, you can send a changeset to the mailing list, but please only do this as a last resort.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Serge Stinckwich http://blog.doesnotunderstand.org/
On Jun 4, 2008, at 5:51 AM, Victor Rodriguez wrote:
Hello,
I took the liberty of rewriting the HowToContribute wiki page [1] with some of the information from the recent discussion in the mailing list.
Excellent!
Please take a look at the wiki page (I have also reproduced the text below) and feel free to make corrections yourself (or post a reply to this message and I'll take care of it).
Please take special care reviewing the "publish to PharoInbox" step, since I have yet to publish anything myself so I might have gotten it wrong.
Best regards,
VÃctor RodrÃguez.
p.s. I got to watch two "Smalltalk daily" [2] screencasts while waiting for the edited page to save.. any timetable on the nifty Pier or Cmsbox Pharo project site? :-)
Yes terrible and ugly wiki. We are waiting for a nice logo and graphical chart and after that we will mirgate to a much better wiki.
[1] http://gforge.inria.fr/plugins/wiki/index.php?id=1299&type=g [2] http://www.cincomsmalltalk.com/blog/blogView?searchCategory=screencast
First and foremost, you must be aware that '''the Pharo project only accepts code published under the MIT license'''. By publishing your code in the !SqueakSource Pharo or !PharoInbox repositories, you are agreeing to this condition.
With that out of the way, here are the steps to submit your contributions:
* Prepare a changeset with your changes. File it out. '''Important''': Put your Full name instead of your initials, it will help up to contact you as it is often necessary.
* Load your changes into a fresh image:
** Download the latest Pharo image from [Files | http://gforge.inria.fr/frs/?group_id=1299].
** Launch the fresh image and load the latest updates by clicking on the ''load code updates'' button on the left flap.
** Importat: Save the image at this point, so that you don't need to reload the updates when you test your changes.
** File in your changeset.
* Create a SLICE package in your package cache:
** Open the Monticello browser. You should see one or more packages marked as modified (they have an asterisk before their name).
** Select your package-cache repository on the right hand pane.
** Create the new package (click on the ''+Package'' button). Name it SLICE-nameofchange, (e.g. SLICE-remove-isMorphic).
** Make all the modified packages (the ones with asterisks before their names) required by your SLICE package. To do this, right click on the SLICE package in the left pane and select ''add required package'', then select the package from the next menu. Repeat for all modified packages.
** Save the SLICE package (click on the ''Save'' button). An mcz package will be saved in your cache for the SLICE package and all the modified packages. You will be prompted for a log message for each one of them, type a useful comment for the first package, copy it and paste it on the others.
** To prepare for the next step, quit the image without saving.
* Test your packages in the clean image.
** Relaunch the clean Pharo image. If you didn't save the image after loading the updates, load the updates (I told you it was important!).
** Open the Monticello browser.
** Open your package-cache repository (select the package-cache in the right pane, click on the ''Open'' button).
** Load your SLICE package. If it loads without errors, you are ready for the next step. If there are errors, try again, or ask for help in the mailing list.
* Publish the SLICE package to !PharoInbox !SqueakSource repository.
** In the Monticello browser add the !PharoInbox repository. Make sure the SLICE package is selected in the left pane, then click on the ''+Repository''. Select ''HTTP'' from the menu, then make sure that the location reads ''http://www.squeaksource.com/PharoInbox''.
** Finally, click on ''Save''.
* Announce your contribution.
** You might need to add an entry to the [tracker | http://gforge.inria.fr/tracker/?group_id=1299], to MantisBugsHarvested in the wiki, etc.
** Send a email to the mailing list.
Congratulations, the world is one step closer to being a better place!
We greately appreciate your effort.
In case of problems, you can send a changeset to the mailing list, but please only do this as a last resort.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2008/6/4 Stéphane Ducasse <stephane.ducasse@inria.fr>:
On Jun 4, 2008, at 5:51 AM, Victor Rodriguez wrote:
Hello,
I took the liberty of rewriting the HowToContribute wiki page [1] with some of the information from the recent discussion in the mailing list.
Excellent!
Please take a look at the wiki page (I have also reproduced the text below) and feel free to make corrections yourself (or post a reply to this message and I'll take care of it).
Please take special care reviewing the "publish to PharoInbox" step, since I have yet to publish anything myself so I might have gotten it wrong.
Best regards,
VÃctor RodrÃguez.
p.s. I got to watch two "Smalltalk daily" [2] screencasts while waiting for the edited page to save.. any timetable on the nifty Pier or Cmsbox Pharo project site? :-)
Yes terrible and ugly wiki. We are waiting for a nice logo and graphical chart and after that we will mirgate to a much better wiki.
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated. Look for example the SyX project : http://code.google.com/p/syx/ and his wiki : http://code.google.com/p/syx/w/list -- Serge Stinckwich http://blog.doesnotunderstand.org/
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated.
Yes may be we should use the Googlecode tracker. Cna someone give a try. Stef
Look for example the SyX project : http://code.google.com/p/syx/ and his wiki : http://code.google.com/p/syx/w/list
-- Serge Stinckwich http://blog.doesnotunderstand.org/
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Wed, Jun 4, 2008 at 7:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated.
Yes may be we should use the Googlecode tracker. Cna someone give a try.
I'm having a look. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Wed, Jun 4, 2008 at 7:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated.
Yes may be we should use the Googlecode tracker. Cna someone give a try.
http://code.google.com/p/pharo/. It seems very cool and simple. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
Thanks so may be we should move the wiki contents to this one but more importantly the tasks. stef On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote:
On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Wed, Jun 4, 2008 at 7:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated.
Yes may be we should use the Googlecode tracker. Cna someone give a try.
http://code.google.com/p/pharo/. It seems very cool and simple.
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Wed, Jun 4, 2008 at 1:39 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Thanks so may be we should move the wiki contents to this one but more importantly the tasks.
I'll volunteer to move the wiki pages, as long as people don't mind if it takes the rest of the week to do it (I can only manage a few hours per week of "free time" :-P ). Victor. ps. Please add me to the project as victorr@gmail.com.
stef
On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote:
On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Wed, Jun 4, 2008 at 7:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated.
Yes may be we should use the Googlecode tracker. Cna someone give a try.
http://code.google.com/p/pharo/. It seems very cool and simple.
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
How could i edit the main page ? 2008/6/4 Damien Cassou <damien.cassou@gmail.com>:
On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Wed, Jun 4, 2008 at 7:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated.
Yes may be we should use the Googlecode tracker. Cna someone give a try.
http://code.google.com/p/pharo/. It seems very cool and simple.
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Serge Stinckwich http://blog.doesnotunderstand.org/
Hi victor If you can, do it but pay attention that we will certainly use pier or cmsbox at the end. (I know that the current wiki is slow). If you do it can you mark each page of the old one with a link to the new one. Stef On Jun 4, 2008, at 7:58 PM, Victor Rodriguez wrote:
On Wed, Jun 4, 2008 at 1:39 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Thanks so may be we should move the wiki contents to this one but more importantly the tasks.
I'll volunteer to move the wiki pages, as long as people don't mind if it takes the rest of the week to do it (I can only manage a few hours per week of "free time" :-P ).
Victor.
ps. Please add me to the project as victorr@gmail.com.
stef
On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote:
On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou@gmail.com
wrote:
On Wed, Jun 4, 2008 at 7:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated.
Yes may be we should use the Googlecode tracker. Cna someone give a try.
http://code.google.com/p/pharo/. It seems very cool and simple.
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Wed, Jun 4, 2008 at 3:20 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Hi victor If you can, do it but pay attention that we will certainly use pier or cmsbox at the end. (I know that the current wiki is slow).
I think it is worth to do it, since there doesn't appear to be a firm idea on when a Pier or Cmsbox site will be ready. Project owners, *please* add me to the project!
If you do it can you mark each page of the old one with a link to the new one.
Not a problem. Su servidor, VÃctor RodrÃguez.
Stef On Jun 4, 2008, at 7:58 PM, Victor Rodriguez wrote:
On Wed, Jun 4, 2008 at 1:39 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Thanks so may be we should move the wiki contents to this one but more importantly the tasks.
I'll volunteer to move the wiki pages, as long as people don't mind if it takes the rest of the week to do it (I can only manage a few hours per week of "free time" :-P ).
Victor.
ps. Please add me to the project as victorr@gmail.com.
stef
On Jun 4, 2008, at 7:36 PM, Damien Cassou wrote:
On Wed, Jun 4, 2008 at 7:08 PM, Damien Cassou <damien.cassou@gmail.com> wrote:
On Wed, Jun 4, 2008 at 7:01 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I think Lukas mention sometimes ago to use Google code, much cleaner interface than this one, the wiki seems also much simpler and there is a simple bug tracker integrated.
Yes may be we should use the Googlecode tracker. Cna someone give a try.
http://code.google.com/p/pharo/. It seems very cool and simple.
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Thu, Jun 5, 2008 at 5:10 AM, Victor Rodriguez <victorr@gmail.com> wrote:
On Wed, Jun 4, 2008 at 3:20 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Hi victor If you can, do it but pay attention that we will certainly use pier or cmsbox at the end. (I know that the current wiki is slow).
I think it is worth to do it, since there doesn't appear to be a firm idea on when a Pier or Cmsbox site will be ready.
Project owners, *please* add me to the project!
If you do it can you mark each page of the old one with a link to the new one.
Not a problem.
Su servidor,
VÃctor RodrÃguez.
Stef On Jun 4, 2008, at 7:58 PM, Victor Rodriguez wrote:
On Wed, Jun 4, 2008 at 1:39 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Thanks so may be we should move the wiki contents to this one but more importantly the tasks.
I'll volunteer to move the wiki pages, as long as people don't mind if it takes the rest of the week to do it (I can only manage a few hours per week of "free time" :-P ).
Victor.
ps. Please add me to the project as victorr@gmail.com.
Done. I've added everyone for which I had a gmail email address on my address book. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
On Wed, Jun 4, 2008 at 8:07 PM, Serge Stinckwich <serge.stinckwich@doesnotunderstand.org> wrote:
How could i edit the main page ?
Administer -> Project Summary -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
I guess i'm not an administrator ;-) 2008/6/5 Damien Cassou <damien.cassou@gmail.com>:
On Wed, Jun 4, 2008 at 8:07 PM, Serge Stinckwich <serge.stinckwich@doesnotunderstand.org> wrote:
How could i edit the main page ?
Administer -> Project Summary
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/
On Thu, Jun 5, 2008 at 11:31 AM, Serge Stinckwich <serge.stinckwich@doesnotunderstand.org> wrote:
I guess i'm not an administrator ;-)
Fixed. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
On Wed, Jun 4, 2008 at 7:39 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Thanks so may be we should move the wiki contents to this one but more importantly the tasks.
I've setup the issue tracking system and I've started by adding 3 short-term issues. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
ok thank you. 2008/6/5 Damien Cassou <damien.cassou@gmail.com>:
On Thu, Jun 5, 2008 at 11:31 AM, Serge Stinckwich <serge.stinckwich@doesnotunderstand.org> wrote:
I guess i'm not an administrator ;-)
Fixed.
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/
participants (5)
-
Alexandre Bergel -
Damien Cassou -
Serge Stinckwich -
Stéphane Ducasse -
Victor Rodriguez