Page 1 of 3

NoScript Source and build environment

Posted: Sun May 03, 2009 3:23 am
by free2create
Where is the source code and build/test environment to NoScript hosted at ?

Re: NoScript Source and build environment

Posted: Sun May 03, 2009 3:29 am
by Alan Baxter
It's all in the installation package hosted on AMO. https://addons.mozilla.org/en-US/firefo ... +sm+fn.xpi

Re: NoScript Source and build environment

Posted: Sun May 03, 2009 3:37 am
by free2create
Thanks, I wasn't very specific many plugings have a subversion/cvs/hg source repository many hosted at mozilla.
That way I can look at the history of each source file. I also doubt that the unit tests, if they exist, are in the install.

-Rob

Re: NoScript Source and build environment

Posted: Sun May 03, 2009 3:45 am
by Alan Baxter
All I know about is all the release versions hosted on AMO. If more than that is available, I'm sure Giorgio will chime in with the info.

Re: NoScript Source and build environment

Posted: Sun May 03, 2009 9:17 am
by Giorgio Maone
Hi Rob,
there's no public CVS yet. It's something I had planned for some time now, but I didn't manage to find the time.
I believe it's a good time to bump its priority, because signals of transparency and openness are needed.
Please keep watching this topic, I'll post here when it's ready (in a week or in a month).

Re: NoScript Source and build environment

Posted: Tue May 05, 2009 9:38 am
by dhouwn
If we're at it, how about a bug tracking system too?

Re: NoScript Source and build environment

Posted: Tue May 05, 2009 9:49 am
by Giorgio Maone
I registered for a mozdev account yesterday morning.
According to the email notification I received, it's still pending "administrator review" (don't know how long it takes).
As far as I know they provide bugzilla.

Re: NoScript Source and build environment

Posted: Thu May 21, 2009 9:10 pm
by Foam Head
It's been a few weeks -- any news on this?

-Foam

Re: NoScript Source and build environment

Posted: Thu May 21, 2009 9:33 pm
by Giorgio Maone
The account seems to be active, even though I've never received any further notification.
I'll upload the sources as soon as I manage to have first ABE prototype out: its deadline (May the 25th) has become quite hard to hit, after the recent disruption :(

Re: NoScript Source and build environment

Posted: Fri May 22, 2009 10:00 pm
by Foam Head
No sweat. Thanks for the update and thanks for all the hard work :D.

-Foam

Re: NoScript Source and build environment

Posted: Mon Jun 15, 2009 9:09 am
by user78
Giorgio Maone wrote: I'll upload the sources as soon as I manage to have first ABE prototype out:
I'm returning to the topic question ;)

Re: NoScript Source and build environment

Posted: Tue Jun 30, 2009 8:19 am
by mikhail
Giorgio, excuse me for the question, but when are you planing to upload sources to mozdev?

Re: NoScript Source and build environment

Posted: Tue Jun 30, 2009 9:06 am
by Giorgio Maone
Hopefully within July.

Re: NoScript Source and build environment

Posted: Thu Aug 06, 2009 7:41 pm
by loquax
Any news?

Giorgio, I highly appreciate all your hard work for NoScript and all other project, but you cannot claim something to be open source and GPL licensed without actually publishing the source code...

Re: NoScript Source and build environment

Posted: Thu Aug 06, 2009 9:35 pm
by Giorgio Maone
loquax wrote:you cannot claim something to be open source and GPL licensed without actually publishing the source code...
Are you sure you know what you're talking about?
This topic was about the availability of a public version-controlled repository, not about the availability of the source code or the validity of its GPL, which is not "a claim", but the license NoScript is released under not just on AMO or my website, but in several GNU Linux distributions including the source-only Gentoo.
The whole source code is publicly available in every each XPI.
You've got it on your hard disk right now, if you're a NoScript user, otheriwise you can download it here.
You can examine and/or modify it by unzipping the XPI and the JAR inside, and "building" it back by rezipping both.
It's been like that for ever, since the very first version.