We are happy to welcome our new sponsored Fedora Ambassador in December:

• https://fedoraproject.org/wiki/User:Jltodea mentored by lbazan

Fedora Ambassador Statistics

Cheers,

herlo

GoOSe Linux 6.0 Beta Release Candidate 5 (RC5) is now available for testing. Visit http://get.gooseproject.org/ to obtain the download.

Once you arrive at the above link, the downloads are under /releases/6.0/Beta-RC5/GoOSe/<arch>/.

The GoOSe Project is always interested in feedback around its project. Please feel free to drop us a line about this release.

Comments/Questions:

• Send us an email goose-linux@googlegroups.com
• Contact us on irc.freenode.net at #gooseproject
• Leave a comment on this blog post

Issues with GoOSe 6.0

If you find yourself having trouble installing, using or managing GoOSe Linux, please let us know. The best way is to file issues at our main project site on github, but we’re happy to have the information in any of the ways listed above.

Testing can be done by anyone. Please feel free to check our new testing wiki page for information on what tests need to be run and which have already passed. If you have interest in helping us test, thank you, thank you, thank you for the help!

GoOSe Beta-RC5 will be available for 1 week from today. At such time the GoOSe team will decide whether it will be the first Golden GoOSe release. This will be based upon feedback provided, so please do tell us what you think!

Cheers,

herlo

Once you arrive at the above link, the downloads are under /releases/6.0/Beta-RC4/GoOSe/<arch>/.

The GoOSe Project is always interested in feedback around its project. Please feel free to drop us a line about this release.

Comments/Questions:

• Send us an email goose-linux@googlegroups.com
• Contact us on irc.freenode.net at #gooseproject
• Leave a comment on this blog post

Issues with GoOSe 6.0

If you find yourself having trouble installing, using or managing GoOSe Linux, please let us know. The best way is to file issues at our main project site on github, but we’re happy to have the information in any of the ways listed above.

GoOSe Beta-RC4 will be available for 2 weeks from today. At such time the GoOSe team will decide whether it will be the first Golden GoOSe release. This will be based upon feedback provided, so please do tell us what you think!

Cheers,

herlo

We are happy to welcome our new sponsored Fedora Ambassadors in November:

• http://fedoraproject.org/wiki/User:Mhayden mentored by herlo
• https://fedoraproject.org/wiki/User:Nsglynn mentored by fab
• https://fedoraproject.org/wiki/User:Juranir mentored by dbruno
• https://fedoraproject.org/wiki/User:Edtomasa mentored by azneita
• https://fedoraproject.org/wiki/User:Cardero mentored by lbazan
• https://fedoraproject.org/wiki/User:Mayorgalinux mentored by lbazan

Fedora Ambassador Statistics

Sun Dec 2 10:19:18 2012 | Approved: 616 | Inactive: 82 | % inactive: 13.31

Cheers,

Herlo

• Installed and configured totpcgi authentication on the staging environment. This performs the verification from the clients. There will be several servers doing authentication to prevent a single point of failure.
• Installed and configured pam_url on each staging client with the intent of connecting to the authentication servers.
• Enabled yubikey as an alternate second factor.
• Reviewed RPMs for pam_url and totpcgi (and a few others to help along the way)
• Setup the totpcgi provisioning web page for google authenticator
• Fixed fun bugs in pam_url
• Wrote documentation on how to setup authentication.

A few things were accomplished that were not part of the goals, but good stuff nonetheless:

• Enjoyed some awesome tapas at Buku (a restaurant is at the base of the Red Hat Tower)
• Found the open source cow
• Documented the setup of the OpenPGP SmartCard with gpg-agent and GNOME 3
• Watched Seth Vidal do some Beastie Boys!
• Enjoyed some yummy dinner at Gravy (thanks to Ruth Suehle and Red Hat)
• Discussed some ideas for FUDCon Lawrence and the future of FUDCons

While I didn’t participate in all of the above activities, I was definitely involved in many of them. It turns out, everyone there was fairly involved at the FAD. It was fun to watch everyone come together to solve this issue. Everyone seemed to have a good sense of satisfaction accomplishing the goals.

Cheers,

herlo

One of the perks I’ve been able to work out will be to attend the Fedora Activity Day this week in Raleigh, where we’ll be working on two-factor authentication among other things. This has been something I’ve recently set up at LF and am hopefully going to be involved in getting this working for Fedora as well.

Additionally, I have been working on getting a GPG SmartCard token working to accommodate ssh authentication. I think Fedora is going to be using Yubikeys, but I thought it might be cool to show this off as an alternative.

Anyway, it should be a fun week and very busy as well. Watch for more reports here about our progress.

Cheers,

Herlo

We are happy to welcome our new sponsored Fedora Ambassadors in October:

• https://fedoraproject.org/wiki/User:Dona from the Philippines mentored by azneita
• https://fedoraproject.org/wiki/User:Cewillia from the USA mentored by jbwillia
• http://fedoraproject.org/wiki/User:Asoliard from Argentina mentored by lbazan
• https://fedoraproject.org/wiki/User:Williamjmorenor from Nicargua mentored by lbazan
• https://fedoraproject.org/wiki/User:Sergiodj from Brasil mentored by dbruno

Fedora Ambassador Statistics

Sun Nov 4 08:57:45 2012 | Approved: 611 | Inactive: 81 | % inactive:13.26

Cheers,

Herlo

Note: The links below are provided by the Fedora Project as a useful pointer to tests the GoOSe Project should be be performing. Please do not modify content on the links below, they are only for reference. It is expected that the GoOSe Project will build its own tests based upon the great tests provided below.

Installation:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test

Base:

https://fedoraproject.org/wiki/Test_Results:Current_Base_Test

Ideally, all Alpha, Beta, and Final priority test cases for
Installation [1], and Base [2] should pass in order to meet the Final Release Criteria [3]. Help is available on #gooseproject on irc.freenode.net.

[1] https://fedoraproject.org/wiki/QA:Installation_validation_testing
[2] https://fedoraproject.org/wiki/QA:Base_validation_testing
[3] https://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria

The GoOSe Project thanks the Fedora Project for providing such good testing information and allowing us to ‘stand upon shoulders of giants’ as we grow and learn.

We are happy to welcome our new sponsored Fedora Ambassadors in September:

Fedora Ambassador Statistics

Sun Sep 30 10:47:14 2012 | Accounts checked : 606 | Inactive Accounts : 80 | % inactive : 13.20

For those of you keeping score at home

As you may have noticed, Joerg (kital) has retired from performing the FAMA duties, and I have taken over. I would personally like to thank him for his excellent work.

Since I’m now in charged of FAMA, I’m modifying the process to fit my availability. Essentially, this means two things:

1. All ambassador applications will be processed on a weekly basis (this usually means a Sunday morning). If I am going to be unavailable on Sunday, I’ll try to get it done as soon as possible before/after that time.
2. Welcome notices will only go out once a month, in an update email / post. This post is the first of the monthly posts.

If you have any questions, you can email me or find me in #fedora-ambassadors on irc.freenode.net (herlo is my fas and irc nick).

Cheers,

Herlo

First off, whoever you are pulling from is the ‘upstream’ repo. My example uses the the saltstack repository (git://github.com/saltstack/salt.git). Make sure it’s set to the read only git url so as to not accidentally push to upstream directly. To set this, you can do the following operation in your repository:

git remote add upstream git://github.com/saltstack/salt.git

Next, adjust the origin repository to point to your fork of the saltstack repository. In my case, my username is ‘herlo’ so my ssh-based read-write git url would be ‘git@github.com:herlo/salt.git’. To adjust the values, do the following:

git remote set-url origin git@github.com:herlo/salt.git

It’s possible that ‘origin’ isn’t set, but if you cloned originally from the saltstack repo, it will need to be adjusted.

Finally, it’s good to verify this, run ‘git config –list’ and look for lines similar to what I show below. If you have yours configured this way, you are ready to work with the github pull request structure simply and efficiently.

git config --list
..snip..
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
remote.origin.url=git@github.com:herlo/salt.git
branch.master.remote=origin
branch.master.merge=refs/heads/master
remote.upstream.url=git://github.com/saltstack/salt.git
remote.upstream.fetch=+refs/heads/*:refs/remotes/upstream/*

Last step, and this is more of a workflow piece than anything. Simply perform tasks in this fashion and you’ll be able to handle most anything with github’s pull requests.

1. git pull upstream master/develop -  (the develop branch is likely the one you want)
2. do some work, make commits to your changes, etc.
3. git push origin master
4. submit a pull request at your fork – (for example, https://github.com/herlo/salt/pull/new/master)
5. once your merged changes are accepted, go back to step one – rinse and repeat.

I hope this helps clarify how the workflow in github could work. It’s simple, easy and effective.

Please let me know of any tweaks as you go through this process. I’d like to hear of any way to improve my process as well.

Cheers,

herlo