Re: New Package Questions

On Wed, 2005-08-10 at 16:34 +0200, Arnaud Limbourg wrote: > Hi, > > > Hi all, > > > > I am a new PEAR developer and I am about to start the process of > > contributing a class that allows PHP to communicate with IBM's U2 > > product RedBack which allows web integration with their PICK clones > > UniData and UniVerse. (see > > http://www-306.ibm.com/software/data/u2/) for > > more information. > > > > Over the last couple of weeks I have been converting my code to the PEAR > > coding standards and starting to document the API for other people to > > use. Maybe one my biggest issues is the naming of my class and the > > section that it should be included in. > > > > The working title for my class is redback, but because RedBack in a > > registered Trademark owned by IBM I am fairly certain that I cannot use > > it. As the other RedBack gateways for ASP and JSP are redpages and > > redbeans respectively. I was thinking something along the same lines > > like redbird (from the covers of the O'Reilly PHP pocket book) or > > something like that. Another option would be to call it New_RedBack, but > > I am not sure if this would be against the trademark. > > RedPear ? :)) I like it. I here by dub the RedPear. Raise Sir RedPair ;-) > > The section that I think it should go into is Networking, but I just > > want to make sure before I create the draft proposal as I am not sure if > > I can change the name or sections. > > If I remember correctly you can. Webservices could be another category. This was my second thought but these seemed more aimed at services like Amazon and such. I think Networking is the closes fit. > > I was also looking are some of the current draft proposals, some of > > theme have been in the process for quite a while, is this normal? Can > > you take a while to complete the draft proposal before it is moved into > > Proposed? > > That is one thing that we plan to avoid in the future, as much time as needed > can be allowed as long as there is activity on the proposal. There are > too many > proposals which have lingered for a loooong time. Thanks I will keep this in mind. > > I also noticed that some did not have any links to code. Is the Draft > > period used to bring together all the required documentation and code > > together before the proposal is moved into the Proposed Status. > > The draft period is usually used to discuss design, naming, etc. Links to code > (if there is any) should be added. I think my idea of using the draft period to bring it scratch, creating the tests, more appropriate examples and more documentation would be acceptable. > > Also I would like to hear any tips from people who have successfully > > gotten a niche package into PEAR as I do feel that my biggest hurdle > > will be getting the votes to get it finally submitted. > > If you make enough noise on this list you should be able to get the votes :) Thanks for the tip. I hope to start the proposal process in the next couple of weeks. Thanks for the feedback. Gordon.