Closed
Bug 636474
Opened 14 years ago
Closed 14 years ago
make the open source closer or unmotivate [hosted add-on development collaboration]
Categories
(Firefox :: General, enhancement)
Tracking
()
RESOLVED
INVALID
People
(Reporter: pedbessa, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b13pre) Gecko/20110224 Firefox/4.0b13pre
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b13pre) Gecko/20110224 Firefox/4.0b13pre
Does each addon have a repository? I wish I could modify the code of an addon and have the addon author decide if my code will be used. Do you think we're going to exchange codes by e-mail? Say the author is the lead developer. Make it optional with default out. Beta test it, see the feedback and change it. Plase, make it!
Reproducible: Always
Reporter | ||
Comment 1•14 years ago
|
||
One real problem is that after if I make a little change to an addon, I would have to keep maintaining it. For example, the original author makes a change to his addon, now I have to make the same change to mine. With more changes and more developers, it's a real problem. So let me have the chance to change the original addon.
An other problem is that after I make a little change to an addon, I have to manually package it which is an action full of chances to commit a mistake. Actually, I wrote a python script, but forgot to share it.
Reporter | ||
Comment 2•14 years ago
|
||
I don't know how you keep Firefox from being fragmented, but you can use that again here.
Reporter | ||
Comment 3•14 years ago
|
||
nm last comment
Comment 4•14 years ago
|
||
This site is for bug reports, not questions/discussion.
Please ask your question here:
http://groups.google.com/group/mozilla.dev.amo/topics
You may also find this of use:
https://addons.mozilla.org/developers/
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
![]() |
||
Updated•13 years ago
|
Summary: make the open source closer or unmotivate → make the open source closer or unmotivate [hosted add-on development collaboration]
You need to log in
before you can comment on or make changes to this bug.
Description
•