Skip to Content.
Sympa Menu

cc-devel - Re: [cc-devel] SoC progress report

cc-devel AT lists.ibiblio.org

Subject: Developer discussion for Creative Commons technology and tools

List archive

Chronological Thread  
  • From: "Bruno Dilly" <bruno.dilly AT gmail.com>
  • To: cc-devel AT lists.ibiblio.org
  • Subject: Re: [cc-devel] SoC progress report
  • Date: Sat, 12 Aug 2006 16:32:30 -0300

Victor,

the remix sources are submitted together with all the other
informations. The "upload" function get form and display it, getting
information from user until he/she decides to post, so the user can
search and accept a lot of sources before post. This approach isn't
very cool for a cli tool, but will work fine in ccPublisher.

And I'm learning a lot with all you guys. It's great!

On 8/11/06, Victor Stone <fourstones.net AT gmail.com> wrote:
On 8/11/06, Jon Phillips <jon AT rejon.org> wrote:
> On Fri, 2006-08-11 at 13:52 -0300, Bruno Dilly wrote:
> > I don't think I have time to extend the API for uploads before SoC
> > deadline, but I can do it later. I'll continue developing CC tools.

understood. and just to be clear I was offering to do the back end of it.

another question (sorry but I'm in a huge rush right so I can't check
it out right now) but I didn't see off hand where the remix sources
were passed into the upload post -- did I just miss that?

> >
> > Really I'm reading the entire file into memory before writing into the
> > socket. I don't know how I could do it better, I will study this
> > point.

I think Nathan is on point here and certainly fits the working model
of ccHost lol -- get it working now optimize later.

> This is also good for newbies to open source to realize how much
> different the open source model is in terms of communicating in smaller
> increments rather than the school-based approach which is to keep things
> closed and in the dark until having one big grand monolithic release...

Well, I didn't go to school lol but I did work at commercial software
companies for 20 years and I will echo what Jon says here --
communication up front about plans and proposed coding implementation
strategies at helps and my be critical in any team situation, open
source or otherwise. The difference in OS projects is that you don't
have all those meetings you have to drag your a$$ to which I would
claim is a net positive.

Awesome work Bruno, thanks so much for doing this stuff!


VS





Archive powered by MHonArc 2.6.24.

Top of Page