Hi All,
Although I'd like to join the packages together it might be more interesting to
have them separated. Not all users are interested in both packages (some will).
I ll will start with a stand alone package.
Johan
> From: carandraug+...@gmail.com
> Date: Wed, 28 Sep 2011 17:12:29 +0100
> Subject: Re: Moving ocframe to Octave-Forge
> To: johanb...@hotmail.com
> CC: octave-dev@lists.sourceforge.net; carba...@ifi.uzh.ch
>
> >> From: carandraug+...@gmail.com
> >> Date: Tue, 27 Sep 2011 17:09:07 +0100
> >> Subject: Moving ocframe to Octave-Forge
> >> To: johanb...@hotmail.com
> >> CC: octave-dev@lists.sourceforge.net; jord...@octave.org
> >>
> >> On 13 September 2011 10:21, JohanB <johan...@users.sourceforge.net> wrote:
> >> > For the moment, ocframe is not under active development. In
> >> > the future I will continue development to support 3D
> >> > analysis . Currently I am busy with some priority project.
> >> > However I can make some time to move my project to
> >> > Octave-Forge. Can I still hold the current project or does
> >> > it has to move to octave-forge as well? (It is easy for help
> >> > files and news if I continue development)
> >> > Which steps do I need to take to move to Octave-forge?
> >>
> >> Hi Johan,
> >>
> >> apologies for the very late response. Actually, Jordi has forwarded me
> >> your reply a long time ago but I only found the time now. By the way,
> >> I'm CC'ing this to the octave-forge mailing list too.
> >>
> >> Regarding your question, you can of course hold your current project
> >> although it's probably better if you make the whole move.
> >>
> >> We usually give write-access to any user after he has contributed some
> >> code. You would be submitting and entire package :) Whenever you feel
> >> like coding it, you can do it. Also, you can stay as the package
> >> maintainer. The documentation for your package is generated when a new
> >> release is made and it will be mentioned on the octave-forge news.
> >> Also, it will make it simpler for you to mantain because you'll only
> >> have to bother with having the code and the packages in 1 place and
> >> it's confusing for users who otherwise will feel as if there's 2
> >> ocframe packages.
> >>
> >> By the way, since 3.4 one can use 'pkg install -forge package-name' to
> >> install packages directly from octave without downloading the package
> >> themselves.
> >>
> >> If you want to make the move, just let us know and give us your
> >> sourceforge account name so we can give write access to the repo.
> >>
> >> Carnë
>
> 2011/9/28 Johan Beke <johanb...@hotmail.com>:
> > Hi Carnë,
> >
> > Feel free to add me to the project. I ll prepare myself to move my project
> > to octave-forge.
> >
> > Kind regards,
> >
> > Johan
>
> Thank you for considering this. I have added you and you should be
> able to commit your functions to the repo now.
>
> About the location of your code, you can create a new directory
> ocframe inside 'trunk/main'. There is another possibility though which
> you might prefer. We have recently (2 days ago actually) added a new
> package 'mechanics'. Do you think your code would fit better there?
>
> I have just spoke to the package maintainer (Juan Carbajal which I'm
> CC'ing on this e-mail) and he agrees that your code would fit nicely
> there and it would be easier for users to find it there. What do you
> think of this?
>
> Carnë
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
