Help with submitting my first package

Hey guys --

I posted here a few months ago, hoping to get some help with
getting my
package ready for submission for review.

Unfortunately, I never found a good, step-by-step
instructions on how to
build the package.xml file, how to test it, and then how to
make sure I
haven't wasted anyone's time by making sure everything is
right.

I've already gone through all my code, made sure the code
was documented,
and gave good examples.

Can someone point me in the right direction for this?

Additionally, I'm rewriting a bunch of existing perl modules
for PHP, such
as Locale::Country, and I want to know where they might go. 
It deals with
ISO3166 Country names/abbreviations translation.  I'm using
it for
Internationalization, so I thought I could put it in there,
but
Internationalization_Country seems long.    Let me
know.

Beckman
------------------------------------------------------------
---------------
Peter Beckman                                               
  Internet Guy
beckmanpurplecow.com                             http://www.purplecow.com/
------------------------------------------------------------
---------------

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Hi there,

The best thing to do is make available the sources as .phps
(for easy 
online viewing) and start a proposal in PePr 
(http:
//pear.php.net/pepr/pepr-proposal-edit.php).

The package.xml is not required for a proposal, we can help
you with 
that afterward 

Arnaud.

Peter Beckman wrote:
> Hey guys --
> 
> I posted here a few months ago, hoping to get some help
with getting my
> package ready for submission for review.
> 
> Unfortunately, I never found a good, step-by-step
instructions on how to
> build the package.xml file, how to test it, and then
how to make sure I
> haven't wasted anyone's time by making sure everything
is right.
> 
> I've already gone through all my code, made sure the
code was documented,
> and gave good examples.
> 
> Can someone point me in the right direction for this?
> 
> Additionally, I'm rewriting a bunch of existing perl
modules for PHP, such
> as Locale::Country, and I want to know where they might
go.  It deals with
> ISO3166 Country names/abbreviations translation.  I'm
using it for
> Internationalization, so I thought I could put it in
there, but
> Internationalization_Country seems long.    Let me
know.
> 
> Beckman
>
------------------------------------------------------------
---------------
> Peter Beckman                                          
       Internet Guy
> beckmanpurplecow.com                             http://www.purplecow.com/
>
------------------------------------------------------------
---------------
> 

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

On 23 Feb 2007, at 09:11, Peter Beckman wrote:

> Additionally, I'm rewriting a bunch of existing perl
modules for  
> PHP, such
> as Locale::Country, and I want to know where they might
go.  It  
> deals with
> ISO3166 Country names/abbreviations translation.

Something similar to I18N_ISO_3166?

ht
tp://www.appelsiini.net/~tuupola/195/i18niso3166

Haven't checked from ISO website for a while if there are
any new  
countries in the globe though 


--
Mika Tuupola                      http://www.appels
iini.net/~tuupola/

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Yep, that's good.    Why isn't
it in the pear repository?

With Perl, I'm know that if it exists, it is likely in CPAN.
 With PHP,
it's often not in PEAR.  Heck, I've written some things for
PEAR and the
process to get it into pear is grueling and badly documented
(or I can't
find the documentation on how to do it, step by step).

Beckman

On Sun, 25 Feb 2007, Mika Tuupola wrote:

>
> On 23 Feb 2007, at 09:11, Peter Beckman wrote:
>
>> Additionally, I'm rewriting a bunch of existing
perl modules for PHP, such
>> as Locale::Country, and I want to know where they
might go.  It deals with
>> ISO3166 Country names/abbreviations translation.
>
> Something similar to I18N_ISO_3166?
>
> ht
tp://www.appelsiini.net/~tuupola/195/i18niso3166
>
> Haven't checked from ISO website for a while if there
are any new countries 
> in the globe though 
>
>
> --
> Mika Tuupola                      http://www.appels
iini.net/~tuupola/
>
>

------------------------------------------------------------
---------------
Peter Beckman                                               
  Internet Guy
beckmanpurplecow.com                             http://www.purplecow.com/
------------------------------------------------------------
---------------

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

The pear manual has all this sort of stuff in it except for
testing, which you 
can choose anyway to do.  I chose to write phpt files which
can be executed with 
the pear run-tests command.  See http://qa.php.net/wr
ite-test.php for more 
information.


BTW, there already exists a package for Internationalisation
of country names.

http://pear.php.ne
t/package/I18Nv2



Arnaud Limbourg wrote:
> Hi there,
> 
> The best thing to do is make available the sources as
.phps (for easy 
> online viewing) and start a proposal in PePr 
> (http:
//pear.php.net/pepr/pepr-proposal-edit.php).
> 
> The package.xml is not required for a proposal, we can
help you with 
> that afterward 
> 
> Arnaud.
> 
> Peter Beckman wrote:
>> Hey guys --
>>
>> I posted here a few months ago, hoping to get some
help with getting my
>> package ready for submission for review.
>>
>> Unfortunately, I never found a good, step-by-step
instructions on how to
>> build the package.xml file, how to test it, and
then how to make sure I
>> haven't wasted anyone's time by making sure
everything is right.
>>
>> I've already gone through all my code, made sure
the code was documented,
>> and gave good examples.
>>
>> Can someone point me in the right direction for
this?
>>
>> Additionally, I'm rewriting a bunch of existing
perl modules for PHP, 
>> such
>> as Locale::Country, and I want to know where they
might go.  It deals 
>> with
>> ISO3166 Country names/abbreviations translation. 
I'm using it for
>> Internationalization, so I thought I could put it
in there, but
>> Internationalization_Country seems long.    Let me
know.
>>
>> Beckman


-- 
     David Sanders

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

On Sun, 25 Feb 2007, Gregory Beaver wrote:

> Peter Beckman wrote:
>> Yep, that's good.    Why isn't
it in the pear repository?
>>
>> With Perl, I'm know that if it exists, it is likely
in CPAN.  With PHP,
>> it's often not in PEAR.  Heck, I've written some
things for PEAR and the
>> process to get it into pear is grueling and badly
documented (or I can't
>> find the documentation on how to do it, step by
step).
>
> PEAR does not try to be CPAN in that the goal is to
have consistently
> reliable, high quality packages rather than to offer
everything under
> the sun, but it is hard to argue that if a package
doesn't even exist
> that it is of a higher quality .  I and
many others have noticed
> problems with the process of getting packages into
PEAR.  We're
> re-evaluating how we make big decisions like the way
packages are
> accepted and other things of this nature with an
ongoing referendum.

  I think that is definitely needed.

  Is high quality versus lots of code the best way?  CPAN I
believe gets
  better and better because once the code passes some minor
tests, the code
  is added and is open to the public.  Automated testing
makes sure code
  continues to work or notify authors if not.  If a tool is
there and the
  framework built, finding problems or enhancements becomes
a community
  thing.  Having volunteers spending days/weeks pouring over
code makes the
  process onerous, tiring and frankly may keep good quality
code from ever
  getting into PEAR in the first place.  Write a script to
make sure the
  code meets coding requirements so I can test it without a
human before
  submission!

  I _CAN_ write good code, and the peer review is nice, but
the lack of
  documentation on how to get your code into the proper
format (package.xml
  being the most confusing and dumbfounding piece, with
little to no
  documentation on how to generate/create it step-by-step --
I'm sure its
  easy once you know, but until then, I don't get it) keeps
my code out of
  PEAR.

  Even posting here hasn't really helped -- Nobody can help
me find
  documentation on how to build my package for PEAR, nobody
seems to have
  any documents on it, and while the coding standards are
very clear, the
  whole directory layout, files required, etc is nowhere to
be found.

> Hopefully we can make some substantial improvements
very soon.  Of
> course, if you have any specific changes you'd like to
see, we welcome
> patches to the documentation (peardoc/ in cvs.php.net)
or infrastructure
> (pearweb/ in cvs.php.net).  The website, for instance,
has a newly
> created roadmap at 
http://pear.php.net/bugs/roadmap.php?package=pearweb
> that shows the direction we're heading on that end, at
least for the
> near future.

  Have there been any results from your efforts?  I know
it's a lot to take
  on.  I just want something like CPAN for PHP, and right
now, PEAR isn't
  it, and doesn't seem to be moving that way either.

Beckman
------------------------------------------------------------
---------------
Peter Beckman                                               
  Internet Guy
beckmanpurplecow.com                             http://www.purplecow.com/
------------------------------------------------------------
---------------

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

Peter Beckman wrote:

>> Hopefully we can make some substantial improvements
very soon.  Of
>> course, if you have any specific changes you'd like
to see, we welcome
>> patches to the documentation (peardoc/ in
cvs.php.net) or infrastructure
>> (pearweb/ in cvs.php.net).  The website, for
instance, has a newly
>> created roadmap at 
http://pear.php.net/bugs/roadmap.php?package=pearweb
>> that shows the direction we're heading on that end,
at least for the
>> near future.
> 
>  Have there been any results from your efforts?  I know
it's a lot to take
>  on.  I just want something like CPAN for PHP, and
right now, PEAR isn't
>  it, and doesn't seem to be moving that way either.

Hi Peter,

Well, for one thing, the governing structure of PEAR has
just undergone
a radical shift, as you can see in the first news item at
http://pear.php.net. 
We'll be having elections shortly to fill the
spots in the PEAR Group/president, and they will start the
move towards
defining collectives.

As for making it easier to release a package, now, once your
package is
accepted, all that is required is to log in with your
account, browse to
your package homepage (http://pear.php.net/
Package_Name for package
"Package_Name"), click on the "0.1.0"
link on the right, which will open
up a box for creating your roadmap for the first release. 
Once you
create it, you'll see a link that says "Generate
package.xml for this
release."

Click on that, and you'll have a fully functional, valid
package.xml
which you can cut/paste into a new file.  This greatly
simplifies the
learning curve.

We are also working to implement user notes for the manual
in the same
way php.net has user notes, which will allow us to catch
major problems
in the documentation, a first requirement for making any big
changes.

As for being CPAN, you're right, PEAR is not CPAN.  It
doesn't mean it
can't be a useful place to find quality code.  If you're
truly
interested in having a say in the process, stick around,
familiarize
yourself with the way things work now, and perhaps propose a
patch or
two.  Of course many ideas require more than just a simple
patch, but
you'd be surprised how many are possible to implement with a
technical
solution.  I implemented secret ballot elections, roadmap
planning,
package.xml generation, and more just with changes to the
pearweb
codebase, for instance.

Greg

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php

I've recently proposed a couple of things and found most of
the
information in the PEAR manual...

What's the package that you want to submit? Do you have any
specific
questions?

>
>   I _CAN_ write good code, and the peer review is nice,
but the lack of
>   documentation on how to get your code into the proper
format
> (package.xml
>   being the most confusing and dumbfounding piece, with
little to no
>   documentation on how to generate/create it
step-by-step -- I'm sure its
>   easy once you know, but until then, I don't get it)
keeps my code out of
>   PEAR.
>
>   Even posting here hasn't really helped -- Nobody can
help me find
>   documentation on how to build my package for PEAR,
nobody seems to have
>   any documents on it, and while the coding standards
are very clear, the
>   whole directory layout, files required, etc is
nowhere to be found.
>


-- 
    David Sanders

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php