2013-03-13, 23:12
The list so far:
Overview list of reasons:
*Not knowing you could submit
*Having to maintain separate versions for each XBMC release if code changed between versions
*Not allowed to contain binary files
*Submission process by email
*No Beta/Testing repo
*No Bug Tracking System
*No good rating / usage stats
*Devs find pushing to own repo is much faster / easier to update their addon instead of doing it to official repo.
*don't want a code review
*once a month submission too restrictive
Suggestion:
*split mailinglist in two: submission and announcements (or handle it different)
Any others?
In the mean time we'll start thinking of some of the issues mentioned and how to possibly solve them.
Overview list of reasons:
*Not knowing you could submit
*Having to maintain separate versions for each XBMC release if code changed between versions
*Not allowed to contain binary files
*Submission process by email
*No Beta/Testing repo
*No Bug Tracking System
*No good rating / usage stats
*Devs find pushing to own repo is much faster / easier to update their addon instead of doing it to official repo.
*don't want a code review
*once a month submission too restrictive
Suggestion:
*split mailinglist in two: submission and announcements (or handle it different)
Any others?
In the mean time we'll start thinking of some of the issues mentioned and how to possibly solve them.