-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2011-03-10 21:14, Doug Springer wrote:
Niels,
I took over from the original developer, and parcellite is no longer
inactive.
Hey,
That sounds good.
There is a fork, it's called clipit, but there were lots of changes
occurring, and I thought that parcellite (after a few bugs were
addressed) was just fine as it was. I don't mind simple features, but
once it looks like klipper, what's the point?
Yes, clipit was the fork I was thinking of. As pabs mentioned in a
separate email, clipit is currently its own package but there was talk
about replacing parcellite with it.
My intent it to primarily bug fix/build fix, add bare essentials from
time to time, and keep parcellite just as it is - but I've sent Andrew
several emails and no response yet. I figured if he doesn't want to
maintain it, I'll take over that part as well.
How do I go about doing that?
As far as I can tell, the maintainer of parcellite is definitely active,
since he uploaded a version of parcellite 5 days ago[1]. I have CC'ed
Andrew, whom I hope will reply within a couple of days.
If you want an active part in maintaining parcellite, your best option
right is to offer to become a co-maintainership.
[1] http://packages.qa.debian.org/p/parcellite/news/20110306T041708Z.html
Best Regards,
Doug Springer
On 03/10/2011 12:53 PM, Niels Thykier wrote:
On 2011-03-10 15:40, doug Springer wrote:
Hi,
I started developing parcellite because I didn't want it to disappear
from the repositories.
I've been developing parcellite for several months now and have a new
release that's been tested and packaged to i386 and amd64. I'd like to
see this make it into main stream.
Where do I go from here? I'll can take over the maintenance if I need
to.
Thanks,
Doug Springer
Hey,
I remember parcellite from a while back; as I recall I managed to reach
the maintainer via his other email: andrewsomething@ubuntu.com
That being said; the last I heard was that parcellite was being
replaced by a fork, since parcellite was inactive. Unfortunately the
name of the fork eludes me at the time.
~Niels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJNed/3AAoJEAVLu599gGRCMIEQAKh2gxbWftckB0/iSkGOcy/v
ItL+CX2/EKKVAJUWS+wrnIihJBu5NQnv2LAp/HQT51h/l1CIbwYA0VnKVZ6lwzuT
Za74JrDcai+AG/e76an2Nuru3UxJGscUVS5UP0WZ82FWBGWneVwn51GOpY6K7HHg
LoMnQaoPQ3MjpfWN8r6tqbMXIAPbbXsmu9S1mHWvWvarNrdan3+xsTlpWccRvr+B
5kgvKbFJjfcROo/nZ4iApD/4Pj6W7M5ujlNjncIYulEJtOpdQHMUU1eX+P/KyB1e
I0wVav15Ego/sbRKBxaZ3izkt1pSxmJAlBfP6kKVJS7Df6X2h1sgzkBpnbRfgyJ5
o7VeAME7ZsczK8JFXiqpdat/DkZODYiBMLQwi2IJ3PwieqorYfp/CyU1299ELcfw
lasbJ9mfTampI/XGE3CIF5no4VJE5GgJJrEzTQ81Dj7FmjvWLy2dwIG8vlm005qg
1GLfXhhCm32SDTkQcFSH9GrIu40hexCAs2IJc51ByUjDJGp28Uh3mKr5PuWKU/de
lVsOFg+P6zBjCojS7E+dVdQnsUH3GJ1MhlZ3hM35Z4T4Yhp6wRoT6dw6skDGk4HL
btG7hul1zpoq2RY7mRpUFQ8P18swGWtbfqWd3gHUMyUrxNnUwA+O88yZLd76foRV
Sh2DKff5MjU64ayQymPn
=CqKP
-----END PGP SIGNATURE-----