How To Make Contributions
Posted 27 April 2004 - 12:48 AM
Even though it is a lot of work for the contributor, all contributions should be submitted with a complete list of "find this" then "replace with or add that" changes to each and every module to which it applies. The reason for this is that most contributions seem to be written for an unmodified system. For modified systems, installation by simply copying various php modules does not work. And, in my case at least, my system is quite modified (I flail around a lot.)
There are some modules I'd like to include, but the effort to try to figure out what was changed, particularly since I'm not sure of exactly what the starting point was (although, usually it is MS2.2 or MS2.1) is prohibitive.
Posted 27 April 2004 - 07:46 AM
stevel, on Apr 22 2004, 09:32 AM, said:
What would be cool is if the submission of a contribution automatically created the announcement topic and support topic, and inserted appropriate links to each.
I think automatic linking/setup is a must, at least from the contrib download to the to the support thread.
Posted 27 April 2004 - 07:52 AM
charleyshipman, on Apr 26 2004, 08:48 PM, said:
(and after checking carefully it's all correct, you can upload that yourself as an update to the contribution if you think it's usefull for others too)
Posted 03 August 2004 - 11:25 AM
(apart from coding standards and documentation explaining how to implement them)
I thinks it's really important to be able to rate contributions, there are some that are very similar and it's difficult to choose between them. I don't have the time to try a contribution, get it to work and then uninstall it without too much fuss.
Secondly, where possible, it would be great to see a screenshot. It really helps to see what the contribution is aiming to do, and it often gives an indication of the level of quality of the contribution itself.
Posted 31 August 2004 - 05:03 AM
The submission and forum linkage is a brilliant idea, as well as rating and download count.
Here I think so many will agree with me.
The contribution section needs cleaned out !!!!!
Contributions that are years old that are already a part of OSC, are clogging the contribution sections.
Contributions that have been updated version by version with old versions left on the list. Or fixed bugs that don't even tell you what version the fix is for till you download and open it up (wasted time and bandwidth)
Double files in some of the newer contributions.
The contribution section needs more of a break down of the types of contributions.
Buttons ... Make a list just for buttons
Admin section ..... listing for admin section and a break down of sub cats.
If the contribution section was ran like the osc cart it would be a wonderful thing.
Just my 2 cents worth
Posted 19 September 2004 - 05:21 PM
osCommerce Monkey & Lead Guitarist for "Sparky + the Monkeys" (Album on sale in all good record shops)
Software is like sex: It's better when it's free. (Linus Torvalds)
Posted 21 December 2004 - 02:09 AM
In some contributions there are questions or remarks posted as updates to the main contribution.
AKA Trygve Lillefosse
Posted 11 March 2005 - 02:14 PM
I have been updating the Who's Online Enhancement contrib. Some people have posted problems with the contrib. Some of these problems are in the code that was from the original MS 2 code base. Most of them deal with site configuration, not install mistakes.
I am not able to test every combination of configuration. So, I'd like to have my newest version beta tested, especially be the people who have current problems to see if the new version fixes them. I have posted a suggestion for beta testing to the WOE support forum and received no takers. I could post it to the contribs but I really only want people to use it who understand it's a beta. Plus, I have a couple more new features to add before I call the version done.
Given that, should I post it as a contrib? Marked as a beta with a warning? Beg some more for beta testers? Any possibility of a Developers contrib section for beta contribs?
Seek and ye shall find Contributions.
Posted 11 March 2005 - 02:20 PM
Remember when you ask for help a lot of people are takers not givers. Only the true osC enthusiasts will come out to help to benefit the whole and not themselves.
So I say post it in the Contributions section even if it's a beta. Who knows? Maybe a beta tester will find faults and make corrections in conjunction with your findings.
Posted 16 May 2005 - 07:20 AM
Could I suggest the following procedure?
1 - Before a contribution is posted, a support thread should be created called "[Contribution_Name] Support".
2 - Include a 'link' to the thread in the readme.txt/documentation.
3 - At the time of posting the new contribution a link to the thread should be included.
Maybe a new Subforum could be created to contain these threads?
I am new to this and am having great difficulty finding threads relating to support issues for the few contributions I have started to use. Only one has anything close to the above.
Posted 09 July 2006 - 05:47 PM
1. Create the forum support thread which will generate a link.
2. Upload the contribution and add to the description box the forum link.
3. Edit or add a post to the forum thread for the contribution link.
If you do the process within few minutes you should endup with a single post on the forum showing the contribution link while the contribution page will include the forum support thread so other people can easily find it.
Posted 13 March 2007 - 01:31 PM
Posted 16 July 2007 - 02:54 PM
I ask I have made 3 or 4 contributions to the 1 section!!
I discovered one problem, fixed the code then contributed it.
Then discovered another problem fixed that code then contributed that version..
Is there no way for the original user to remove their contribution or alternativly a moderator for the contributions
A supreme being that you can say - delete this one please?
Posted 13 April 2008 - 07:57 PM
Of course all contributions should be accompanied by a readme.txt or install.txt, which clearly describes the function, content and structure of the contribution, then lists steps for its installation. The contributor should also note the compatibility constraints (e.g., works only with checkout system post 20021101) or certification (e.g., tested with MS1).
Let me take this opportunity to stimulate some discussion on conventions (or at least suggestions) for packaging contributions.
Posted 15 July 2008 - 07:47 AM
Posted 15 July 2008 - 11:43 AM
- complete instructions - including file change instructions for a standard shop
- include changed files, if possible
- stay away from html instruction files
- don't include changes that have nothing to do with the contribution
- GPL license file (required)
You should also have tested the contribution in both MS2 and RC2 shops, or state that your contribution will only work with one. And if you upload a new version, upload a full version.
Most Important: Header Tags SEO - Ultimate SEO V 2.2d
All SEO Addons: Recommended SEO Addons
Finding relevant link exchanges - Headers Already Sent - What does it cost? -What's my version? - How to change titles? - Preventing HotLinking
Posted 05 July 2009 - 02:26 PM
I have no idea how to cook but I have a restaurant and would like the world to come to my kitchen to eat (and get sick)
ARE YOU FOR REAL?
I certainly appreciate your concerns about modularity, stability and the upkeep of conventions. It would in deed leed to a better system.
On the other hand, the emphasis on the 'perfect' coding standard might encourage less experienced developers and, most of all, users to make their spontaneous ideas available to the community.
I, for this matter, can hardly write php, never mind fully understand the tep-methods. But I'm a user with a clear idea of how certainl shop functions will have to work. If I ever make a proper contribution, it probably won't be spotless. Should I not make it available?
Perhaps, there could be sort of a 'mentoring group' where beginners can post their contributions for polishing up. More experienced developers can then comment or contribute some corrections. Then, the code will be fantastic and the community still benefits from the maximum base of ideas.
In the end, I'd rather have a sloppy solution to an urgent problem, than none at all.
But, again I am NOT IN TOTAL disagreement.
Posted 30 September 2009 - 11:42 AM
I would love to hear your take(s) on this
Edited by dvharrison, 30 September 2009 - 11:42 AM.
Posted 03 October 2009 - 06:51 AM
Posted 03 October 2009 - 01:59 PM
The main RSS feed is noisy, telling you about many contributions that don't matter to you. A more targeted feed or feeds would allow you to watch just the contributions that you are actually using. The current feed is good for finding new contributions to install (albeit with a high noise to signal ratio), but the desire is for updating currently installed contributions with the latest bugfixes and security patches.