"Action Items" From FUDCon?
 

Can anyone think of any action items the infrastructure team (or others
for that matter) may need to do as a result of discussions during
hackfest/fudcon?

-Mike

/me hates the phrase "Action Items" but "Stuff to do from FUDCon" just
didn't sound right.

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On Sun, 2008-01-13 at 18:28 -0600, Mike McGrath wrote:
> Can anyone think of any action items the infrastructure team (or others
> for that matter) may need to do as a result of discussions during
> hackfest/fudcon?
>
> -Mike
>
> /me hates the phrase "Action Items" but "Stuff to do from FUDCon" just
> didn't sound right.

I use that phrase myself, sorry if it's obscene. :-D

I'm thinking back to our SSO session, where of course I did a lot of
talking (maybe 1/2 to be fair) and not any writing. But we talked
about:

* being a WordPress/Lyceum (multiuser) provider
* Seth knows about this as well as of this morning, and didn't
immediately want to kill anyone
* using it to test OpenID capabilities (there's an OpenID 2.0 plugin
for WP)

Hopefully this will spark some memories of other things that came up,
but that's what comes to my mind immediately.

--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project: http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On Jan 13, 2008 3:28 PM, Mike McGrath <mmcgrath@redhat.com> wrote:
> Can anyone think of any action items the infrastructure team (or others
> for that matter) may need to do as a result of discussions during
> hackfest/fudcon?

figure out how to get koji to write back an immutable unique tag back
into cvs for each non-scratch koji build that completes. Or something
equivalent so we can regenerate srpms from cvs reasonably easily for
any package version we have released. There is an issue right now
with forced retagging in cvs still being possible which means we can't
rely on the tags that get created when a contributor does a make tag.

-jef

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On Sun, 13 Jan 2008, Paul W. Frields wrote:


* being a WordPress/Lyceum (multiuser) provider


If the decision is made to do this, then any work that we do in this
area could be immediately useful to Red Hat Magazine, which has had
occasionaly infrastructure difficulties but right now is running on
Lyceum.


I'd be willing to wager that the Fedora setup could meet our needs and
also theirs, and perhaps lead to a deal in which whatever hardware they
are using can be included into our pool provided that we keep Red Hat
Magazine up, which would be a very small amount of additional work on
top of what it seems like we might do anyway.


Does what I'm trying to say make sense? If we do X work to get our own
multi-user blog infrastructure up, for a very small amount we might be
able to do a better and cheaper job for the Red Hat Magazine folks, and
in doing so be able to make use of some of their hardware.


--Max

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On Jan 13, 2008 6:33 PM, Paul W. Frields <stickster@gmail.com> wrote:
> * being a WordPress/Lyceum (multiuser) provider
> * Seth knows about this as well as of this morning, and didn't
> immediately want to kill anyone
> * using it to test OpenID capabilities (there's an OpenID 2.0 plugin
> for WP)

The Fedoratv codebase is a wordpress derivative as well. So keep that
in mind. Having our own wordpress instance, might mean we can grow a
competent contributor base for both a wordpress and Fedoratv base and
move the Fedoratv development forward more quickly.

-jef

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On Jan 13, 2008, at 19:51 , Jeff Spaleta wrote:


On Jan 13, 2008 6:33 PM, Paul W. Frields <stickster@gmail.com> wrote:

* being a WordPress/Lyceum (multiuser) provider
* Seth knows about this as well as of this morning, and didn't
immediately want to kill anyone
* using it to test OpenID capabilities (there's an OpenID 2.0 plugin
for WP)


The Fedoratv codebase is a wordpress derivative as well. So keep that
in mind. Having our own wordpress instance, might mean we can grow a
competent contributor base for both a wordpress and Fedoratv base and
move the Fedoratv development forward more quickly.


FWIW, I evaluated various blog systems a while back for use by the
community of a large publishing-related site, and Wordpress/Lyceum
were among the less desirable ones. Especially avoid Wordpress-MU (it
creates a new set of DB tables for every single user...)


Just wanted to suggest taking a look at roller.apache.org or
blojsom.com. The main Roller hacker also lives in the NC Triangle
area, and was very helpful answering my questions in the past, as well
as incorporating changes to accomodate my requirements.


Best,
-- Elliot

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On Sun, 2008-01-13 at 20:03 -0800, Elliot Lee wrote:

> FWIW, I evaluated various blog systems a while back for use by the
> community of a large publishing-related site, and Wordpress/Lyceum
> were among the less desirable ones. Especially avoid Wordpress-MU (it
> creates a new set of DB tables for every single user...)
>
> Just wanted to suggest taking a look at roller.apache.org or
> blojsom.com. The main Roller hacker also lives in the NC Triangle
> area, and was very helpful answering my questions in the past, as well
> as incorporating changes to accomodate my requirements.
>

The biggest plus to wordpress is its openid integration. According to Mr
Frields it is top notch and is something we probably want to pursue in
all of our apps, eventually.

-sv


_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On Jan 13, 2008 7:28 PM, Mike McGrath <mmcgrath@redhat.com> wrote:
> Can anyone think of any action items the infrastructure team (or others
> for that matter) may need to do as a result of discussions during
> hackfest/fudcon?

We (me and John Poelstra) need to come up with a bugzilla workflow
that's sane, and present it to FESco for review/ripping apart :)

> /me hates the phrase "Action Items" but "Stuff to do from FUDCon" just
> didn't sound right.

AI's is fine with me, but I guess that I have corporate brain rot :/

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On 1/13/08, Jeff Spaleta <jspaleta@gmail.com> wrote:
> On Jan 13, 2008 3:28 PM, Mike McGrath <mmcgrath@redhat.com> wrote:
> > Can anyone think of any action items the infrastructure team (or others
> > for that matter) may need to do as a result of discussions during
> > hackfest/fudcon?
>
> figure out how to get koji to write back an immutable unique tag back
> into cvs for each non-scratch koji build that completes. Or something
> equivalent so we can regenerate srpms from cvs reasonably easily for
> any package version we have released. There is an issue right now
> with forced retagging in cvs still being possible which means we can't
> rely on the tags that get created when a contributor does a make tag.

>From what I know of CVS, this isn't possible from inside CVS and
likely very difficult from outside CVS too. Basically, you'd have to
set up a database outside CVS that would track the version (and maybe
the MD5/SHA signature) of every file that koji used to build the SRPM.
With this setup you could at least know if CVS had been messed with
after Koji did the build.

I know I'm going to evoke some groans when I say this, but Git
provides exactly the mechanism that you're looking for. The Git
commit id is actually a SHA1 hash of the history of a particular
commit. If you know the Git commit id you can be guaranteed that you
got exactly the same source out that you put in. I believe that
Mercurial has a similar system, however I'm not sure that that
Mercurial makes as strong guarantees as Git does.

I believe that both Git and Mercurial provide the ability to GPG sign
a tag - another way to accomplish this goal would be for Koji to sign
the tags that it builds from.

Jeff

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board

"Action Items" From FUDCon?
 

On Jan 13, 2008 8:50 PM, Jeffrey Ollie <jeff@ocjtech.us> wrote:
> >From what I know of CVS, this isn't possible from inside CVS and
> likely very difficult from outside CVS too. Basically, you'd have to
> set up a database outside CVS that would track the version (and maybe
> the MD5/SHA signature) of every file that koji used to build the SRPM.
> With this setup you could at least know if CVS had been messed with
> after Koji did the build.

Are you aware of what are cvs is setup to do right now? make srpm
basically provides the needed functionality in a checked out cvs tree.
For the purpose of recreating srpms for binaries we distribute
on-demand we just have to have tags we can trust corresponding to a
build we can trust. In discussion with infrastructure and release
people before it was brought up that it would be a good idea to have
koji re-tag back into cvs after a build to indicate it was a
releasable build and that its a trivial change in how things are done.

-jef

_______________________________________________
fedora-advisory-board mailing list
fedora-advisory-board@redhat.com
http://www.redhat.com/mailman/listinfo/fedora-advisory-board