remote-help-assistant team mailing list archive
-
remote-help-assistant team
-
Mailing list archive
-
Message #00041
Re: Coming back to the assistant
On Sun, 2009-10-11 at 19:11 +0100, Andrew Sayers wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hey all,
>
> A variety of things going on in my life have pulled me away from the
> assistant for many months now. But with some gentle nudging from the
> Ubuntu Vancouver Local Committee, I'm trying to find some time to spend
> on RHA. Thanks, new members! My time's likely to be limited and
> unpredictable for the near future, but I'll do my best.
>
> Before I was dragged away from the project, the 0.1 branch was in its
> maintenance phase, as 0.2 was being developed. 0.2 is a significant
> overhaul, throwing out bits that didn't work, reworking bits that didn't
> work right, and adding bits that were omitted before. I've attached a
> beta version of 0.2, so people can try it out without downloading the
> source repository.
>
> I've tested 0.2 enough to know that it will take you through at least a
> few screens, but I still haven't set up a virtual machine to test it
> against, so it may fall on its face after that. Here are some things
> I'd really like people to test:
>
> * Can you run the assistant? Is it obvious how to start it, and get
> around it? Would your gran say the same thing?
> * Can you connect to other people with the assistant?
> * The easiest way to access the documentation is through Advanced > More
> information on page 3. Does the documentation make sense to you? Does
> it seem like a reasonable way to organise the assistant?
>
> I'm currently developing the 0.2 codebase here:
>
> https://code.launchpad.net/~andrew-bugs-launchpad-net/remote-help-assistant/0.2
>
> If you're interested in the programming side of things, feel free to
> download the code, play about with it, and upload your changes.
> Otherwise, suggestions are always gladly received on the list :)
>
> Incidentally, the documentation is currently released under the GFDL
> because that's what GNOME recommends. I'm not that comfortable with the
> GFDL, and it seems that I'm not the only one, as the Ubuntu
> Documentation Project prefers the Creative Commons ShareAlike license.
> I'm quite cautious about legal issues, and after literally minutes of
> searching, I've not been able to find a trustworthy guide to putting
> your documentation under the CC-BY-SA license. If anyone out there
> knows of such a guide, please speak up!
>
> - Andrew
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkrSH8MACgkQGRQTxegE/G5gAACeKf5Mxq1aGQymNWoqcerM5IF4
> UNMAoIu1Mzd1Q8K3lLE3YBxmmFBiyuyX
> =n1mn
> -----END PGP SIGNATURE-----
> plain text document attachment (remote-help-assistant_0.2_all.deb.asc)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEABECAAYFAkrSFw0ACgkQGRQTxegE/G4t/wCggac2Xj4ShIpMO45DaMxyX09S
> 7qcAn0ff12gqPxpPkPp4sPyc6FHbMWHW
> =OGRq
> -----END PGP SIGNATURE-----
> _______________________________________________
> Mailing list: https://launchpad.net/~remote-help-assistant
> Post to : remote-help-assistant@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~remote-help-assistant
> More help : https://help.launchpad.net/ListHelp
good to have you back Andrew!
Attachment:
signature.asc
Description: This is a digitally signed message part
Follow ups
References