[Slackbuilds-users] Propose a new approach regarding scripts submission and management

[Ben Mendis]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My $0.02,

If I remember correctly, when official git access was first announced,
the admins stated that they wanted to continue using the submission form
for new packages and updates. It seems that pull requests are considered
fine for minor corrections.

While using pull requests for submissions and updates would certainly be
more convenient for those of us who already maintian our scripts under
git anyways, it would probably be less convenient for anyone who
doesn't.

The other reason the admins probably want to continue using the
submission form is becaues of the additional information/fields in that
form. Trying to force people to use a consistent pattern in their commit
messages would probably be a pain in the ass (or maybe just requires
some hooks?) but giving them a web form to fill out is comparatively
easy.

I don't know how exactly the workflow works on the admin side, but I
expect that any solution would need to prioritize makeing their work
easier. They do have to do far more work than any individual
submitter/maintainer so we should really be optimizing for their work
load.

Best regards,
Ben

On Sun, 10 Jun 2012, Cowyn Li wrote:

> Hello folks,
>
> it's a long time since my last participation here, with a new E-mail
> account this time.
>
> My proposal is using Git for all the steps in SlackBuild scripts
> management. Think about how Linus manages git repositories for Linux
> kernel sources.
>
> IIRC, the workflow of submitting scripts remains unchanged from the
> beginning of the project. Can't deny that it's fundamental and
> reliable. I do know Slackware fellows always keep thing as simple as
> possible. And I guess I countered myself. :-P
>
> Is it just me or are some guys feeling that this workflow is
> inconvenient, inefficient, on both submitter side and admin side. I'm
> not going to take examples at this time, maybe you have been thinking
> about it.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJP05aiAAoJEMco5sYyM+0w7nwH/An19OGkavg9lYqTqqEPTOnC
ijkUm+OQh46DbWSlGb4lW1kRFHUXONBglAcz7dRfQU1ilDRS8NZ3FnumrYuiNMkf
vhwRJhkX5Yup8Oc+xAyZbP4sYfF/E8FOLwDujjnYrytlVlyST1a0YxCBRa/1k6Og
JzTxsS+g1VqX6mV4EZfgAkIJsrF585Tf6dMF5LWJxwHBBOcRK+p4tKOfD1W5Axqx
izacwvULwZ5f8XPQxeGQn0Z3I/M0d/zTgjhBXNKhsqxQEt7Sh1Ba05W7XeOrUZkM
CLXowiqeXtaVRHTCDHv79PjDfElhfVEEJvH7XG3hkRaoTXP/vxpTsM0Tjzw8ZEs=
=xnTS
-----END PGP SIGNATURE-----