Google Code Page for Puppy Development

Message

technosaurus · #1 Post by **technosaurus** » Sat 10 Oct 2009, 02:40

One thing I continue to hear about in Puppy reviews is the appearance that we are hap-hazardously organized and sometimes bug fixes get lost in the shuffle. Another is that we have our packages scattered about the internet and difficult to find (especially for newcomers) We have a lot of dedicated people that are willing to contribute, but no place to keep their work. I am slowly but surely attempting to correct this by establishing package maintainers, but have found that the forum has its limitations. The most dependable solution I can find is code.google.com. Developers/Contributors/Packagers can PM me for access; just include your google/gmail account info (or I can set you up with one if you don't have one - it will be ...@openplatformeducation.org)

We are starting out with 2GB for packages and 1GB for code, SVN, issue (bug) tracking, wiki ...

http://code.google.com/p/support/wiki/GettingStarted

If you would like to be the maintainer for your favorite package and keep it up to date, we have several developers that are more than willing to mentor you to get you started, so don't be afraid to volunteer.

# Project members authenticate over HTTPS to allow committing changes.
svn checkout https://puppy-development.googlecode.com/svn/trunk/ puppy-development --username youremail@gmail.com

# Non-members may check out a read-only working copy anonymously over HTTP.
svn checkout http://puppy-development.googlecode.com/svn/trunk/ puppy-development-read-only

raffy · #2 Post by **raffy** » Sat 10 Oct 2009, 05:49

Thanks for this , TZ.

Clicking on the link you gave brought me to "getting started", so I tried using the subdomain "puppy-development" in the bottom links, and landed here:

http://code.google.com/p/puppy-development/

Perhaps for users, this would mean:

- Issues = Bugs
- Downloads = Packages

Of course "Source" is for developers.

As to the wiki, we will see how this compares with the wikka wiki.

BTW, my gmail account allows me access to the site.

aarf · #3 Post by **aarf** » Sat 10 Oct 2009, 07:29

i am reluctant to use corporate america for things that can be had else where as it tends to add a distasteful flavour to the whole project
also if it is under your control you can correct issues.
like this: below
cannot see the full page in my screen (to the right) and there is no way to get to see it either. same in seamonkey.

technosaurus · #4 Post by **technosaurus** » Sat 10 Oct 2009, 08:26

aarf wrote:i am reluctant to use corporate america for things that can be had else where as it tends to add a distasteful flavour to the whole project

amazingly google code has the least amount of ads and the servers are more dependable than other solutions

also I posted this issue to their help area (temporary workaround - if you unmaximize the window you can move it off the screen and resize it to view)

aarf · #5 Post by **aarf** » Sat 10 Oct 2009, 09:03

technosaurus wrote:
aarf wrote:i am reluctant to use corporate america for things that can be had else where as it tends to add a distasteful flavour to the whole project
amazingly google code has the least amount of ads and the servers are more dependable than other solutions

also I posted this issue to their help area (temporary workaround - if you unmaximize the window you can move it off the screen and resize it to view)

cant see this has solved the issue of small screen or the other issue. i personally will not be signing up for a gmail account just to use it.
if you must go the third party route i cant see why you need to go past https://launchpad.net/ where the rest of the opensource community already is, sharing bugs and fixes among them. dependability would not be an issue there either as ubuntu /Canonical Ltd has major resource backing.

technosaurus · #6 Post by **technosaurus** » Sat 10 Oct 2009, 09:20

I see that you have already set it up...

01micko · #7 Post by **01micko** » Sat 10 Oct 2009, 09:33

...and recharge battery and resize pupsave

PMed T

Lobster · #8 Post by **Lobster** » Sat 10 Oct 2009, 09:42

I cant see why you need to go past https://launchpad.net/

Seems a good choice that aarf suggests
technosaurus is already using the google solution

To me it is what the developers will find most useful

technosaurus · #9 Post by **technosaurus** » Sat 10 Oct 2009, 09:56

If you can deal with the slowness, clutter and *buntuisms and don't mind bazaar which runs on python and several other dependencies then launchpad is fine. I avoid python whenever possible, but if someone wants to take the lead and build the 10mb worth of dependencies and test them and package them and test them then sure why not. The bug tracking feature of launchpad is better, but not really worth the trade off.

Puppy's DEVx already comes with svn and thus google code can be used now.

aarf · #10 Post by **aarf** » Sat 10 Oct 2009, 09:58

technosaurus wrote:I see that you have already set it up...

i opened the account long ago but have barely used or explored it . if you want the keys i will gladly hand them over. opened more for the advertising value and place marker than to use it myself at that time.

edit: agree that it slow perhaps the https security is partly to blame for the slowness. trade security for speed ?
giving options, the choices are not mine to make.

Lobster · #11 Post by **Lobster** » Sat 10 Oct 2009, 10:27

Puppy's DEVx already comes with svn and thus google code can be used now

Got it.

Would
Jacob, Aragon, Dio, or Scott
(mentioned here)
http://puppylinux.org/wikka/Puppy44Team
be willing to help with the bug reporting procedure?

They could also work on the wiki if registering
All help welcome

aarf · #12 Post by **aarf** » Sat 10 Oct 2009, 11:36

01micko wrote:...and recharge battery and resize pupsave

PMed T

i like to live on the wild unpredictable edge.

raffy · #13 Post by **raffy** » Sat 10 Oct 2009, 12:23

Yes, opening a gmail account just to use the google code site is an issue to some people. But there are already a number of developers there in the google site, so things are moving.

Non-gmail users can still download files. And even if they can't post issues directly, they can use the bug reporting facility in the Forum, after which the devs ("committers") can post the issues in the site.

So this is indeed an additional, useful resource. aarf noted that some fine-tuning needed...

puppyite · #14 Post by **puppyite** » Sat 10 Oct 2009, 13:54

technosaurus wrote:Solution:
http://code.google.com/p/puppy-development/

Technosaurus,
IIUC I see one (experimental?) bug reported. Should I infer that you and other developers support this as your (their) preferred solution? If so then there is no need for me to reinvent the wheel with a duplicate and/or less acceptable bug tracker. Please give me a clear indication of what you think is best in this regard. Dropping my proposed bug tracker is no skin off my nose as I have other avenues for assisting Puppy Linux.

technosaurus · #15 Post by **technosaurus** » Sat 10 Oct 2009, 15:02

I can establish a separate login if you don't have a gmail account. (if you already have a gmail account it just lets me be a little bit lazy)

Launchpad would be ok for later woof built U and D pups. I'd be fine with using it as the sole bug tracker, but for all of the source stuff google code is more usable at the moment.

dogone · #16 Post by **dogone** » Sat 10 Oct 2009, 15:47

aarf wrote:i am reluctant to use corporate america for things that can be had else where as it tends to add a distasteful flavour to the whole project also if it is under your control you can correct issues. like this: below cannot see the full page in my screen (to the right) and there is no way to get to see it either. same in seamonkey.

Millions of people would disagree with you, aarf. Thousands of respectable projects employ Google's service. BTW, your display problem is Opera's fault, not Googles. Enable Opera's "Fit-to-width" and all will be well.

#17 Post by **Pizzasgood** » Sat 10 Oct 2009, 16:23

I don't see why creating a gmail account is a big deal. It's not like you would be forced to actually use it for email. You could think of it as primarily a google code account that also happens to come with an email account. Frames of reference.

Anyway, I'm in. Once you get me hooked up, I think I'll move development of my antispam bot there. Probably also RetroVol, although I'm not sure I can do that without losing the history. Not a huge deal as I currently have it sitting between two phases of development (just finished adding i18n support Monday, so I can get back to doing things that matter, like the gui configuration and improving general ergonomics).

What structure are we using? Looking at what's there now, it seems to be {trunk,tags,branches}/<package>/. It would probably be better to use <project>/{trunk,tags,branches}/, so that they are more atomic.
http://svnbook.red-bean.com/en/1.0/svn- ... 5-sect-6.1

dogone · #18 Post by **dogone** » Sat 10 Oct 2009, 16:31

While not a dev, I do enjoy tracking and browsing Puppy dev efforts. And it appears to me that Puppy is rapidly out-growing this forum. Looking down from 10000 feet, the forum is (sorry) a mess. I'm in my third or fourth year as a Puppy user and I still have trouble finding and following projects, tasks and discussions. It's a jumble that could well be putting off a lot of potential (and current) Puppy devs and users.

Devs are the ones to decide the Google Code question, but as an enthusiastic Puppy user/follower, I suggest taking a hard look at the project's infrastructure with growth in mind. Puppy could well see a flood of new users and contributors in coming months/years and the project must be ready to accept, support and encourage them all.

We just have to bite the bone and start doing it like the big dogs!

Aitch · #19 Post by **Aitch** » Sat 10 Oct 2009, 17:30

Hi Techno

I'd already posted a thread about GoogleWave, which I think is an extension of GoogleCode

http://www.murga-linux.com/puppy/viewtopic.php?p=343155

A. Can you confirm?
B. Do you have access/invites,
.... as I'm looking at it as possible Puppy Manual/Info/help file updating tool - am in touch with Colonel Schell atm on this project - there seems to be some paralleling of posters,... inc Puppyite, though I see this as a separate project to the dev/code one

Anyone else who has Wave access/invites please post or PM me

Thanks

Aitch

#20 Post by **Pizzasgood** » Sat 10 Oct 2009, 18:16

Re: my comment on directory structure

Apparently Google likes to have a single branches directory defined for the "assigned review" thing. So it might be good to do something along the lines of this:

Code: Select all

|-- branches
|-- tags
`-- trunk
    |-- project_1
    |   |-- branches
    |   |-- tags
    |   `-- trunk
    |-- project_2
    |   |-- branches
    |   |-- tags
    |   `-- trunk
    `-- project_3
        |-- branches
        |-- tags
        `-- trunk

That way each individual project can have its own branches, tags, and trunk directories, and Google's software can be happy. And the "global" branches directory could also be used for wide sweeping changes that would impact many projects at once, while individual branches/ directories would be for package-specific branches.

So is this what we're doing?

Just want to make sure I know how we're laying things out before I start doing anything.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Google Code Page for Puppy Development

Google Code Page for Puppy Development

thanks

to g or not to g