11:37 a.m.
Here is the link to my RFR
https://fedoraproject.org/wiki/Infrastructure/RFR/FedoraMagazine
-=-
Also, is it ok that I created a group on the account system called magazine?
Thanks,
Anand Capur
11:44 a.m.
Anand Capur wrote:
Here is the link to my RFR
https://fedoraproject.org/wiki/Infrastructure/RFR/FedoraMagazine
-=-
Also, is it ok that I created a group on the account system called
magazine?
Thanks,
Anand Capur
Why would http://fedoraproject.org/wiki/FedoraMagazine not work as it
does for http://fedoraproject.org/wiki/FWN ?
-Mike
12:17 p.m.
We are going to be a real online magazine with an ISSN number with the
possibility of going to a print edition in the future. I have a flash based
magazine reader and many other things that could not run on the wiki. We are
a totally separate idea than FWN.
12:29 p.m.
Anand Capur wrote:
We are going to be a real online magazine with an ISSN number with
the
possibility of going to a print edition in the future. I have a flash
based
magazine reader and many other things that could not run on the wiki.
We are
a totally separate idea than FWN.
I saw that, and as for the namespace you need a completely separate
domain? fedoraproject.org/FedoraMagazine/ won't work? Also you'll be
using PHP, please explain more what you'll be doing with php. We are
extremely concerned about php in our environment.
-Mike
12:37 p.m.
I understand, it will be for my egroupware installation, and maby joomla cms
if needed. The good thing is both are quite secure when installed properly.
Here is the reccomended config for egroupware. (It printed this on my home
comp). And yes we need a completely separate domain.
Checking required PHP version 4.3+ (recommended 5+): 4.4.7 ==> True
Checking php.ini: safe_mode = Off: ini_get('safe_mode')='' = Off
Checking php.ini: magic_quotes_runtime = Off:
ini_get('magic_quotes_runtime')='0'
= Off
Checking php.ini: register_globals = Off: ini_get('register_globals')='0'
=
Off
Checking php.ini: memory_limit >= 16M: ini_get('memory_limit')=''
Checking php.ini: max_execution_time >= 30:
ini_get('max_execution_time')='60'
Checking php.ini: file_uploads = On: ini_get('file_uploads')='1' = On
Checking php.ini: include_path contain .:
ini_get('include_path')='.:/usr/lib/php:/usr/local/lib/php'
Checking php.ini: mbstring.func_overload = 7: ini_get('
mbstring.func_overload')='7'
Checking extension mysql is loaded or loadable: True
Checking extension pgsql is loaded or loadable: False
The pgsql extension is needed, if you plan to use a pgSQL database.
Checking extension odbc is loaded or loadable: False
The odbc extension is needed, if you plan to use a MaxDB, MsSQL or Oracle
database.
Checking extension oci8 is loaded or loadable: False
The oci extension is needed, if you plan to use a Oracle database.
Checking extension mbstring is loaded or loadable: True
Checking extension session is loaded or loadable: True
Checking extension imap is loaded or loadable: True
Checking PEAR is installed: 1.5.4
Checking PEAR::Net_Socket is installed: 999.egw-pear
Checking PEAR::Auth_SASL is installed: 1.0.2
Checking PEAR::Net_IMAP is installed: 999.egw-pear
Checking PEAR::Net_Sieve is installed: 999.egw-pear
Checking PEAR::HTTP_WebDAV_Server is installed: 999.egw-pear
Checking PEAR::Log is installed: 999.egw-pear
Checking for GD support...: True
Checking file-permissions of . for not world writable: root/root
drwxr-xr-x
This might take a while, please wait ...
Checking file-permissions of header.inc.php for not world readable:
nobody/nobody -rw-r--r--
header.inc.php is world readable !!!
Checking if php.ini setting session.save_path='/tmp' is writable by the
webserver: root/root drwxrwxrwt
Thanks,
Anand
12:39 p.m.
Also, it is ok that I made a group on the account system called magazine? I
just want to make sure ;)
12:48 p.m.
Anand Capur wrote:
Also, it is ok that I made a group on the account system called
magazine? I
just want to make sure ;)
Don't do it yet, if we accept this proposal we'll give you a xen
instance to get a proof of concept up and running. Once it goes to
production you can create the group. What do you plan on using the
group for?
-Mike
12:54 p.m.
I already did, but i'd be happy to remove it (group). A xen instance sounds
good (I am experienced with all the command line/ssh stuff, so I wouldn't
need much help). I plan on using the group for tracking, and to ensure that
the cla_done group is completed by the contributers (it is a magazine that
will be under a no-copyright, so as the wiki needs we would need that
agreement signed also). I will be providing it in multiple formats, not only
flash. Flash would just enhance the viewing experience, but in NO way would
be required!!!
Thanks,
Anand
12:58 p.m.
Anand Capur wrote:
I already did, but i'd be happy to remove it (group). A xen
instance
sounds
good (I am experienced with all the command line/ssh stuff, so I wouldn't
need much help). I plan on using the group for tracking, and to ensure
that
the cla_done group is completed by the contributers (it is a magazine
that
will be under a no-copyright, so as the wiki needs we would need that
agreement signed also).
I'm extremely surprised and worried that you could create a FAS group...
(not your fault). I'd like to hear what others think about this
proposal. Also, right now is it just you doing the work or do you have
an interested team and support group?
I will be providing it in multiple formats, not only
flash. Flash would just enhance the viewing experience, but in NO way
would
be required!!!
I think many would argue that if it doesn't work with a default
fedora
install, we shouldn't use it. Fedora as an organization values
freedom... as well as stable FireFox installs ;-)
-Mike
9:42 p.m.
Once upon a time Monday 18 June 2007, Mike McGrath wrote:
Anand Capur wrote:
> I already did, but i'd be happy to remove it (group). A xen instance
> sounds
> good (I am experienced with all the command line/ssh stuff, so I wouldn't
> need much help). I plan on using the group for tracking, and to ensure
> that
> the cla_done group is completed by the contributers (it is a magazine
> that
> will be under a no-copyright, so as the wiki needs we would need that
> agreement signed also).
I'm extremely surprised and worried that you could create a FAS group...
(not your fault). I'd like to hear what others think about this
proposal. Also, right now is it just you doing the work or do you have
an interested team and support group?
As am I. Does someone have some time to look at the code for accounts system
so we can better define who can create a new group.
> I will be providing it in multiple formats, not only
> flash. Flash would just enhance the viewing experience, but in NO way
> would
> be required!!!
I think many would argue that if it doesn't work with a default fedora
install, we shouldn't use it. Fedora as an organization values
freedom... as well as stable FireFox installs ;-)
I would say you cant use flash at
all as we cant provide a way to view the
content
Dennis
9:51 p.m.
I can look at the code, but I don't know where it is. Last I read it
was on an internal redhat server. And I have no problem using NO
FLASH!
6:37 p.m.
Anand Capur wrote:
I can look at the code, but I don't know where it is. Last I read
it
was on an internal redhat server. And I have no problem using NO
FLASH!
So it sounds like the software you'd like to use have changed quite a
bit in the progress of this thread. Please update your RFR with a full
list of exactly what packages you need to do this.
-Mike
10:37 p.m.
So it sounds like the software you'd like to use have changed
quite a
bit in the progress of this thread. Please update your RFR with a full
list of exactly what packages you need to do this.
-Mike
eGroupware (which I will package for Fedora if needed).
* Web Server: Apache 2.2.4
* PHP 5.2.2
* Database Server: MySQL 5.0.41
* Mail Server: Postfix
* DNS Server: BIND9 (chrooted)
* FTP Server: pureftpd
* POP3/IMAP server: Dovecot
* Webalizer for web site statistics
10:43 p.m.
Anand Wrote:
eGroupware (which I will package for Fedora if needed).
* Web Server: Apache 2.2.4
* PHP 5.2.2
* Database Server: MySQL 5.0.41
* Mail Server: Postfix
* DNS Server: BIND9 (chrooted)
* FTP Server: pureftpd
* POP3/IMAP server: Dovecot
* Webalizer for web site statistics
I found egroupware packaged for fedora core
5/6 already. The link was
on the egroupware site.
http://software.opensuse.org/download/server:/eGroupWare/Fedora_Extras_6/...
11:18 a.m.
Anand Capur wrote:
Anand Wrote:
> eGroupware (which I will package for Fedora if needed).
> * Web Server: Apache 2.2.4
> * PHP 5.2.2
> * Database Server: MySQL 5.0.41
> * Mail Server: Postfix
> * DNS Server: BIND9 (chrooted)
> * FTP Server: pureftpd
> * POP3/IMAP server: Dovecot
> * Webalizer for web site statistics
I found egroupware packaged for fedora core 5/6 already. The link was
on the egroupware site.
http://software.opensuse.org/download/server:/eGroupWare/Fedora_Extras_6/...
Ouch. If it's not in our repositories, it isn't properly packaged, or
no-one ever took ownership and just dumped that package in.
IMHO, that package is just like this one package I have:
This-will-burn-your-machine-1.0.1-4.fc7.noarch.rpm
Nonetheless, the package can save you a lot of work since you would only
need to adjust the spec file and maybe build some patches to match the
packaging guidelines and pass review, right?
Kind regards,
Jeroen van Meeuwen
11:42 a.m.
> I found egroupware packaged for fedora core 5/6 already. The
link was
> on the egroupware site.
> http://software.opensuse.org/download/server:/eGroupWare/Fedora_Extras_6/...
>
Ouch. If it's not in our repositories, it isn't properly packaged, or
no-one ever took ownership and just dumped that package in.
IMHO, that package is just like this one package I have:
This-will-burn-your-machine-1.0.1-4.fc7.noarch.rpm
Nonetheless, the package can save you a lot of work since you would only
need to adjust the spec file and maybe build some patches to match the
packaging guidelines and pass review, right?
Kind regards,
Jeroen van Meeuwen
Yeah, it should. Since it is just a PHP Script I wouldn't need to make
it "compatible" with fedora 7. I don't need to include php right?
11:49 a.m.
Anand Capur wrote:
Yeah, it should. Since it is just a PHP Script I wouldn't need to
make
it "compatible" with fedora 7. I don't need to include php right?
Actually you do.
http://fedoraproject.org/wiki/PackageMaintainers/Join
-Mike
1:52 p.m.
> > I found egroupware packaged for fedora core 5/6 already. The
link was
> > on the egroupware site.
> >
http://software.opensuse.org/download/server:/eGroupWare/Fedora_Extras_6/...
> >
>
> Ouch. If it's not in our repositories, it isn't properly packaged, or
> no-one ever took ownership and just dumped that package in.
>
> IMHO, that package is just like this one package I have:
> This-will-burn-your-machine-1.0.1-4.fc7.noarch.rpm
>
> Nonetheless, the package can save you a lot of work since you would only
> need to adjust the spec file and maybe build some patches to match the
> packaging guidelines and pass review, right?
>
> Kind regards,
>
> Jeroen van Meeuwen
>
Yeah, it should. Since it is just a PHP Script I wouldn't need to make
it "compatible" with fedora 7. I don't need to include php right?
you don't include php. but you need to make sure that files are put in
the correct locations with the correct permissions. you cant just dump it
all in /var/www/html/egroupware or something along those lines
--
Dennis Gilmore, RHCE
1:57 p.m.
On 6/21/07, Dennis Gilmore <dennis(a)ausil.us> wrote:
>> > I found egroupware packaged for fedora core 5/6 already. The link was
>> > on the egroupware site.
>> >
http://software.opensuse.org/download/server:/eGroupWare/Fedora_Extras_6/...
>> >
>>
>> Ouch. If it's not in our repositories, it isn't properly packaged, or
>> no-one ever took ownership and just dumped that package in.
>>
>> IMHO, that package is just like this one package I have:
>> This-will-burn-your-machine-1.0.1-4.fc7.noarch.rpm
>>
>> Nonetheless, the package can save you a lot of work since you would
only
>> need to adjust the spec file and maybe build some patches to match the
>> packaging guidelines and pass review, right?
>>
>> Kind regards,
>>
>> Jeroen van Meeuwen
>>
> Yeah, it should. Since it is just a PHP Script I wouldn't need to make
> it "compatible" with fedora 7. I don't need to include php right?
you don't include php. but you need to make sure that files are put in
the correct locations with the correct permissions. you cant just dump it
all in /var/www/html/egroupware or something along those lines
--
Dennis Gilmore, RHCE
Allright, thanks! Also, do I need to include PHP PEAR extensions that are
required?
10:53 p.m.
Anand Capur wrote:
> So it sounds like the software you'd like to use have changed
quite a
> bit in the progress of this thread. Please update your RFR with a full
> list of exactly what packages you need to do this.
>
> -Mike
eGroupware (which I will package for Fedora if needed).
You'll need to get it
into Fedora.
* Web Server: Apache 2.2.4
* PHP 5.2.2
* Database Server: MySQL 5.0.41
Our production DB MySQL instance will be 5.0.22
that ships with RHEL5
after we upgrade it.
* Mail Server: Postfix
* DNS Server: BIND9 (chrooted)
We host DNS already
* FTP Server: pureftpd
We don't do ftp
* POP3/IMAP server: Dovecot
We do not host email
I don't mean to rain on your parade but this is a very lofty goal, I'd
recommend working with the docs team and see if you can get some more
support, http://fedoraproject.org/wiki/DocsProject/Magazine.
If you're going to use eGroupware it'll have to be packaged and approved
in Fedora before we can use it in our infrastructure.
-Mike
10:58 p.m.
> eGroupware (which I will package for Fedora if needed).
You'll need to get it into Fedora.
> * Web Server: Apache 2.2.4
> * PHP 5.2.2
> * Database Server: MySQL 5.0.41
Our production DB MySQL instance will be 5.0.22 that ships with RHEL5
after we upgrade it.
> * Mail Server: Postfix
> * DNS Server: BIND9 (chrooted)
We host DNS already
> * FTP Server: pureftpd
We don't do ftp
> * POP3/IMAP server: Dovecot
We do not host email
---
Ok, no email is fine, no ftp is fine (I'll use SFTP right?), MySQL
5.0.22 is also fine (it'll be a remote server?). And DNS hosting from
you is also fine!
1:06 p.m.
On Tue, 2007-06-19 at 22:53 -0500, Mike McGrath wrote:
Anand Capur wrote:
>> So it sounds like the software you'd like to use have changed quite a
>> bit in the progress of this thread. Please update your RFR with a full
>> list of exactly what packages you need to do this.
>>
>> -Mike
> eGroupware (which I will package for Fedora if needed).
What is eGroupware used for in the magazine?
You'll need to get it into Fedora.
> * Web Server: Apache 2.2.4
> * PHP 5.2.2
We don't need Joomla or any other PHP CMS. We are using Plone for CMS,
it can handle all of what the other ones can. Bonus -- you benefit from
the Fedora knowledge and hacking on Plone, versus doing it all yourself.
I don't mean to rain on your parade but this is a very lofty
goal, I'd
recommend working with the docs team and see if you can get some more
support, http://fedoraproject.org/wiki/DocsProject/Magazine.
Anand has general support for his idea, via f-marketing-l, but he is
definitely going a bit in his own direction. This is not necessarily a
bad thing -- if he has the energy to grow the contributors and sustain
the momentum, we'll all learn a few things.
My recommendation is for Fedora Magazine to be a SIG operating within
the Fedora News Project. Right now, FWN is the sole output of Fedora
News, but that doesn't have to be. So, Fedora Magazine would be a peer
output effort.
IMHO, an effort needs at least SIG status before it should get precious
Infrastructure resources. If we get to the point where Xen instances
can be handed out like Halloween candy, then that changes. Right?
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
1:13 p.m.
On 6/20/07, Karsten Wade <kwade(a)redhat.com> wrote:
On Tue, 2007-06-19 at 22:53 -0500, Mike McGrath wrote:
> Anand Capur wrote:
> >> So it sounds like the software you'd like to use have changed quite a
> >> bit in the progress of this thread. Please update your RFR with a
full
> >> list of exactly what packages you need to do this.
> >>
> >> -Mike
> > eGroupware (which I will package for Fedora if needed).
What is eGroupware used for in the magazine?
> You'll need to get it into Fedora.
> > * Web Server: Apache 2.2.4
> > * PHP 5.2.2
We don't need Joomla or any other PHP CMS. We are using Plone for CMS,
it can handle all of what the other ones can. Bonus -- you benefit from
the Fedora knowledge and hacking on Plone, versus doing it all yourself.
> I don't mean to rain on your parade but this is a very lofty goal, I'd
> recommend working with the docs team and see if you can get some more
> support, http://fedoraproject.org/wiki/DocsProject/Magazine.
Anand has general support for his idea, via f-marketing-l, but he is
definitely going a bit in his own direction. This is not necessarily a
bad thing -- if he has the energy to grow the contributors and sustain
the momentum, we'll all learn a few things.
My recommendation is for Fedora Magazine to be a SIG operating within
the Fedora News Project. Right now, FWN is the sole output of Fedora
News, but that doesn't have to be. So, Fedora Magazine would be a peer
output effort.
IMHO, an effort needs at least SIG status before it should get precious
Infrastructure resources. If we get to the point where Xen instances
can be handed out like Halloween candy, then that changes. Right?
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Thanks! We do need a real CMS, not a Wiki. I already ditched Joomla and I
think i'll use plone. I'm sorta experienced with it and like you said I can
use the knowledge already gained from the main site installation of plone.
eGroupWare is how we will track the projects, articles, progress, calendar,
etc....
2:56 p.m.
Anand Capur wrote:
Thanks! We do need a real CMS, not a Wiki. I already ditched Joomla
and I
think i'll use plone. I'm sorta experienced with it and like you said
I can
use the knowledge already gained from the main site installation of
plone.
eGroupWare is how we will track the projects, articles, progress,
calendar,
etc....
So we've come a long way in the last couple of days. I always
appreciate enthusiasm for something new and you certainly seem to have
it. Please be patient with the team though as it's very difficult for
us to determine serious contributors from fly by night people. And fly
by night people really do take a bad toll on our work.
The task list as I see it is you'd still like to see eGroupWare to track
articles, progress and calendar stuff. In theory this could be used in
other areas of our infrastructure as well. So the first task I see for
you is to get eGroupWare packaged and in Fedora.
Beyond that I'd like to ask you to contact Thomas Chung about Fedora
Weekly News if you have not already done so. It sounds like the two of
you are targeting very similar audiences and Fedora Weekly News is
absolutely outstanding in my opinion and more contributors will only
make it better. I think it would be best if the two of you worked
together to find commonalities like branding/look, release cycle, tools,
etc. Then Thomas's group could continue to report on all things Fedora
and you could add to it maybe interviews and technical documentation.
Perhaps Thomas would like to use Plone in the future for Fedora Weekly
News when it comes out.
What do you think?
-Mike
11:23 p.m.
On 6/21/07, Mike McGrath <mmcgrath(a)redhat.com> wrote:
Anand Capur wrote:
> Thanks! We do need a real CMS, not a Wiki. I already ditched Joomla and
I
> think i'll use plone. I'm sorta experienced with it and like you said
> I can
> use the knowledge already gained from the main site installation of
> plone.
> eGroupWare is how we will track the projects, articles, progress,
> calendar,
> etc....
So we've come a long way in the last couple of days. I always
appreciate enthusiasm for something new and you certainly seem to have
it. Please be patient with the team though as it's very difficult for
us to determine serious contributors from fly by night people. And fly
by night people really do take a bad toll on our work.
The task list as I see it is you'd still like to see eGroupWare to track
articles, progress and calendar stuff. In theory this could be used in
other areas of our infrastructure as well. So the first task I see for
you is to get eGroupWare packaged and in Fedora.
Beyond that I'd like to ask you to contact Thomas Chung about Fedora
Weekly News if you have not already done so. It sounds like the two of
you are targeting very similar audiences and Fedora Weekly News is
absolutely outstanding in my opinion and more contributors will only
make it better. I think it would be best if the two of you worked
together to find commonalities like branding/look, release cycle, tools,
etc. Then Thomas's group could continue to report on all things Fedora
and you could add to it maybe interviews and technical documentation.
Perhaps Thomas would like to use Plone in the future for Fedora Weekly
News when it comes out.
What do you think?
-Mike
I already am working with FWN and Thomas :). The plan is to include FWN
articles in the magazine ;). And I'm not a "Fly by night" person, I
didn't
just "show" up, i've been an ambassador for a long time (at least 1-2
years).
2:40 p.m.
-----Original Message-----
From: fedora-infrastructure-list-bounces(a)redhat.com
[mailto:fedora-infrastructure-list-bounces@redhat.com] On Behalf Of Anand
Capur
Sent: Wednesday, June 20, 2007 21:23
To: fedora-infrastructure-list(a)redhat.com
Subject: Re: Fedora Magazine RFR
On 6/21/07, Mike McGrath <mmcgrath(a)redhat.com> wrote:
Anand Capur wrote:
Thanks! We do need a real CMS, not a Wiki. I already ditched
Joomla and I
think i'll use plone. I'm sorta experienced with it and like
you
said
I can
use the knowledge already gained from the main site installation
of
plone.
eGroupWare is how we will track the projects, articles, progress,
calendar,
etc....
So we've come a long way in the last couple of days. I always
appreciate enthusiasm for something new and you certainly seem to
have
it. Please be patient with the team though as it's very difficult
for
us to determine serious contributors from fly by night people. And
fly
by night people really do take a bad toll on our work.
The task list as I see it is you'd still like to see eGroupWare to
track
articles, progress and calendar stuff. In theory this could be used
in
other areas of our infrastructure as well. So the first task I see
for
you is to get eGroupWare packaged and in Fedora.
Beyond that I'd like to ask you to contact Thomas Chung about Fedora
Weekly News if you have not already done so. It sounds like the two
of
you are targeting very similar audiences and Fedora Weekly News is
absolutely outstanding in my opinion and more contributors will only
make it better. I think it would be best if the two of you worked
together to find commonalities like branding/look, release cycle,
tools,
etc. Then Thomas's group could continue to report on all things
Fedora
and you could add to it maybe interviews and technical
documentation.
Perhaps Thomas would like to use Plone in the future for Fedora
Weekly
News when it comes out.
What do you think?
-Mike
I already am working with FWN and Thomas :). The plan is to include FWN
articles in the magazine ;). And I'm not a "Fly by night" person, I
didn't
just "show" up, i've been an ambassador for a long time (at least 1-2
years).
------------------------------------------------------------------
Well I've had my own job to take care of but I've been keeping up with the
list. I can't tell you how much of a pain it is to try to send a file
update to a unit over a 2.4kbs satellite channel particularly when they
can't stay at periscope depth for any period of time to download a 4mb
file... Had to break it up into a lot of very small zip files.
I do like the idea of a Fedora magazine but I'm afraid it could just fall
into the multitude of ezines out there like some projects I've seen. It
seems like the focus right now is on a dedicated infrastructure for a
magazine that doesn't exist yet. I for one would worry less about that and
more about the whole magazine issue itself. I don't think it's set in yet
about how much work goes into producing a magazine. I think the more
logical step would be to build a team and actually see if you can pull off
producing a few issues and then break off to it's own website once it's
established. I've seen more than a few ezine projects die after an issue or
two and it seems like a huge waste in man-hours to set up everything before
that. Start it off with FWN and then worry about the rest later.
-------
Brandon Jasper, CTN2(SS)
NSSC Bangor N621 Afloat LAN Admin.
SIPRNET: brandon.jasper(a)navy.smil.mil
10:53 p.m.
Well I've had my own job to take care of but I've been keeping up with the
list. I can't tell you how much of a pain it is to try to send a file
update to a unit over a 2.4kbs satellite channel particularly when they
can't stay at periscope depth for any period of time to download a 4mb
file... Had to break it up into a lot of very small zip files.
I do like the idea of a Fedora magazine but I'm afraid it could just fall
into the multitude of ezines out there like some projects I've seen. It
seems like the focus right now is on a dedicated infrastructure for a
magazine that doesn't exist yet. I for one would worry less about that
and
more about the whole magazine issue itself. I don't think it's set in yet
about how much work goes into producing a magazine. I think the more
logical step would be to build a team and actually see if you can pull off
producing a few issues and then break off to it's own website once it's
established. I've seen more than a few ezine projects die after an issue
or
two and it seems like a huge waste in man-hours to set up everything
before
that. Start it off with FWN and then worry about the rest later.
-------
Brandon Jasper, CTN2(SS)
NSSC Bangor N621 Afloat LAN Admin.
SIPRNET: brandon.jasper(a)navy.smil.mil
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
I have already run a few local print newspapers, so I know the workload and
how it all goes. An online magazine would be slightly easier because I don't
need to worry about the printing deadlines.
12:05 p.m.
-----Original Message-----
From: fedora-infrastructure-list-bounces(a)redhat.com
[mailto:fedora-infrastructure-list-bounces@redhat.com] On Behalf Of
Anand Capur
Sent: Thursday, June 21, 2007 20:53
To: fedora-infrastructure-list(a)redhat.com
Subject: Re: Fedora Magazine RFR
Well I've had my own job to take care of but I've been keeping
up with the
list. I can't tell you how much of a pain it is to try to send
a file
update to a unit over a 2.4kbs satellite channel particularly
when they
can't stay at periscope depth for any period of time to download
a 4mb
file... Had to break it up into a lot of very small zip files.
I do like the idea of a Fedora magazine but I'm afraid it could
just fall
into the multitude of ezines out there like some projects I've
seen. It
seems like the focus right now is on a dedicated infrastructure
for a
magazine that doesn't exist yet. I for one would worry less
about that and
more about the whole magazine issue itself. I don't think it's
set in yet
about how much work goes into producing a magazine. I think the
more
logical step would be to build a team and actually see if you
can pull off
producing a few issues and then break off to it's own website
once it's
established. I've seen more than a few ezine projects die after
an issue or
two and it seems like a huge waste in man-hours to set up
everything before
that. Start it off with FWN and then worry about the rest
later.
-------
Brandon Jasper, CTN2(SS)
NSSC Bangor N621 Afloat LAN Admin.
SIPRNET: brandon.jasper(a)navy.smil.mil
_______________________________________________
Fedora-infrastructure-list mailing list
Fedora-infrastructure-list(a)redhat.com
<mailto:Fedora-infrastructure-list@redhat.com>
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
I have already run a few local print newspapers, so I know the workload
and how it all goes. An online magazine would be slightly easier because
I don't need to worry about the printing deadlines.
--------------
I don't see how the lack of a printing deadline would make any
difference as there is still a posting deadline which all things
considered is still a deadline to meet. It would stand to reason that
not meeting the schedule people expect things to be published by would
only serve to hurt the credibility of the publication. That aside I
still retain the opinion that a few issues should be published before
creating the administration overhead of setting up a server for it.
It's like committing to sailing around the world before you make sure
your ship can float on it's own.
-------
Brandon Jasper, CTN2(SS)
NSSC Bangor N621 Afloat Lan Admin.
SIPRNET: brandon.jasper(a)navy.smil.mil
1:45 p.m.
On Fri, 2007-06-22 at 10:05 -0700, Jasper, Brandon R CTN2 NSSC BANGOR
WA, NSSC Bangor N621 wrote:
It's like committing to sailing around the world before you make
sure
your ship can float on it's own.
I've been watching/peripherally involved with Red Hat Magazine since it
started, and I see that it went through many of the pains you
describe/suggest avoiding. Initially, it was a print magazine, with all
that entails. Then it moved online, where it went through several
toolings and features. Currently, it is just about the nicest that it
has been, from a reader, contributor, and staff (I reckon) perspective.
It has its own domain (redhatmagazine.com) and publishes using Lyceum
(http://lyceum.ibiblio.org/), that is, blog software. Quite a journey
to end up 'back at basics', and some lessons to learn from.
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
1:01 p.m.
On Mon, 2007-06-18 at 23:24 +0530, Anand Capur wrote:
(it is a magazine that will be under a no-copyright, so as the wiki
needs we would need that agreement signed also).
What do you mean by "no-copyright"?
The CLA doesn't grant copyright to anyone; you retain that for the work
you do. It provides an agreement whereby Fedora (via Red Hat) can use
your copyright material under an open source license.
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
1:05 p.m.
On 6/20/07, Karsten Wade <kwade(a)redhat.com> wrote:
On Mon, 2007-06-18 at 23:24 +0530, Anand Capur wrote:
> (it is a magazine that will be under a no-copyright, so as the wiki
> needs we would need that agreement signed also).
What do you mean by "no-copyright"?
The CLA doesn't grant copyright to anyone; you retain that for the work
you do. It provides an agreement whereby Fedora (via Red Hat) can use
your copyright material under an open source license.
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
I mean people are free to use, copy, etc.. the articles and since the CLA is
for copyrighted stuff, I guess we wouldn't need it signed.
1:34 p.m.
On Wed, 2007-06-20 at 23:35 +0530, Anand Capur wrote:
I mean people are free to use, copy, etc.. the articles and since
the
CLA is for copyrighted stuff, I guess we wouldn't need it signed.
Hmm. I don't want to take this too far off the path, and it's certainly
off-topic for this list. Hopefully I can clear this up with a single
post.
There are a few things to keep in mind:
* At least in the US, copyright exists the moment you create a work.
This means you have to actively choose to _give_up_ your copyright. For
Fedora Magazine to do that, it would have to have a legal notice that it
was all public domain, etc.
* Fedora cannot take contributions into anything we (re)distribute that
do not come from a person who has signed the CLA. So, I can take a
patch from a non-CLA person, but when that patch goes into a package, it
is done by me (a CLA person). Same with a fix for content from someone
who emails me that "such and so" is incorrect in a doc.
These are not anywhere official yet, but they are approved by legal
counsel:
http://fedoraproject.org/wiki/KarstenWade/Drafts/CLAAcceptanceHierarchies
If content goes into something we distribute, whether in an ISO or HTML
file, it has to be under the CLA. A click-through CLA is sufficient for
content that is Web-only.
* The way Fedora achieves the goal you lay out for people to be "free to
use, copy, etc." the content that comes from Fedora Magazine is to
license that content. Same as we do with source code. Thus, Fedora
Magazine would be under the OPL (most likely), but we could look into
the possibility of using the CC BY-SA.
Clear as mud? :)
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
1:49 p.m.
On 6/21/07, Karsten Wade <kwade(a)redhat.com> wrote:
On Wed, 2007-06-20 at 23:35 +0530, Anand Capur wrote:
> I mean people are free to use, copy, etc.. the articles and since the
> CLA is for copyrighted stuff, I guess we wouldn't need it signed.
Hmm. I don't want to take this too far off the path, and it's certainly
off-topic for this list. Hopefully I can clear this up with a single
post.
There are a few things to keep in mind:
* At least in the US, copyright exists the moment you create a work.
This means you have to actively choose to _give_up_ your copyright. For
Fedora Magazine to do that, it would have to have a legal notice that it
was all public domain, etc.
* Fedora cannot take contributions into anything we (re)distribute that
do not come from a person who has signed the CLA. So, I can take a
patch from a non-CLA person, but when that patch goes into a package, it
is done by me (a CLA person). Same with a fix for content from someone
who emails me that "such and so" is incorrect in a doc.
These are not anywhere official yet, but they are approved by legal
counsel:
http://fedoraproject.org/wiki/KarstenWade/Drafts/CLAAcceptanceHierarchies
If content goes into something we distribute, whether in an ISO or HTML
file, it has to be under the CLA. A click-through CLA is sufficient for
content that is Web-only.
* The way Fedora achieves the goal you lay out for people to be "free to
use, copy, etc." the content that comes from Fedora Magazine is to
license that content. Same as we do with source code. Thus, Fedora
Magazine would be under the OPL (most likely), but we could look into
the possibility of using the CC BY-SA.
Clear as mud? :)
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Heh, yep clear as mud! Ok, well OPL is fine for me. I just used CC BY-SA as
a possibility. Legal issues are always confusing...
1:55 p.m.
Also, if we form a SIG, then we can't use the Fedora name?
--From - http://fedoraproject.org/wiki/DefiningProjects
A SIG earns official project status through successful accomplishment of
objectives that warrant more prominence in the Fedora Project. If
contributors request it, the parent project or the Fedora Project
Board<http://fedoraproject.org/wiki/Board>will evaluate the SIG's
progress reports and make a determination of
readiness for this stage. At this point, it may be branded with the Fedora
name and promoted to the full status of a Fedora project. It can join the
ranks of the most valuable initiatives currently leading the Fedora Project.
2:53 p.m.
Anand Capur wrote:
I understand, it will be for my egroupware installation, and maby
joomla cms if needed. The good thing is both are quite secure when
installed properly.
That is not my experience with Joomla. Lots of security holes in that
one (and Mambo from which it is offspring).
Nils Breunese.
2:59 p.m.
Am Montag, den 18.06.2007, 23:07 +0530 schrieb Anand Capur:
I understand, it will be for my egroupware installation, and maby
joomla cms if needed. The good thing is both are quite secure when
installed properly. Here is the reccomended config for egroupware. (It
printed this on my home comp). And yes we need a completely separate
domain.
^^
YOUR eGroupware-Installation and maybe YOUR joomla; excuse me but we
have a wiki basicly on fedoraproject?
If these are your projects, why they have to be in the
Fedora-Infrastructure?
Just a question, nothing more ...
Regards
GeroldKa
8:30 p.m.
Yes, I can make groups, see all the users, and groups also. BUT If I try to
edit a user that isn't me it just gives basic info about them. If I try to
edit a group that isn't mine it shows me like I can edit it, but when I
click update, save, whatever it doesn't let me complete the edit. Actually
the flash was only to have it so you can turn the pages like a real
magazine. If you don't want that, thats no problem it isn't required in any
way. So far I have 5 people on our team. I would secure Joomla, not just a
vanilla uninstall. Yes, I agree that they aren't secure from the start, but
they can be. Joomla is just a possibility, but probably unlikely since we
are formatting and designing the magazine offline. I simply said my because
I am the one installing it. It isn't mine personally and the magazine isn't
mine personally also. I'm just the EiC but it is from all the contributers,
not just me.
Thanks,
Anand
5:40 a.m.
Anand Capur wrote:
I understand, it will be for my egroupware installation, and maby
joomla
cms if needed. The good thing is both are quite secure when installed
properly. Here is the reccomended config for egroupware. (It printed
this on my home comp). And yes we need a completely separate domain.
eGroupware and joomla have not been packaged for Fedora, have they?
Just my € 0,02
Kind regards,
Jeroen van Meeuwen
-kanarip
5:53 a.m.
They are PHP Scripts and don't need to be "packaged". They will run on
Mac, Windows, Linux if you have a PHP interpreter. eGroupware does
have a package, but that is for installation of perfect image.
7:11 a.m.
Once upon a time Tuesday 19 June 2007, Anand Capur wrote:
They are PHP Scripts and don't need to be "packaged".
They will run on
Mac, Windows, Linux if you have a PHP interpreter. eGroupware does
have a package, but that is for installation of perfect image.
We have a policy in Fedora that we can only use software that is packaged and
in Fedora. for you to use them you would have to have them pass review
first. This is to make sure that what we use is given back to the greater
Fedora Community.
Dennis
7:23 a.m.
Op dinsdag 19-06-2007 om 17:48 uur [tijdzone +0530], schreef Anand
Capur:
So is our wiki packaged in fedora? Is our account system packaged in
fedora?
The wiki is, it's the moin package, account system not for what it's
worth.
But look at other PHP-stuff: gallery is packaged (along with a whole
bunch of add-ons), phpMyAdmin, phpLdapAdmin, ...
If you want to use, get it packaged
Just my 2 ct
Bart
--
Bart <couf(a)fedoraproject.org> <couf(a)skynet.be>
key fingerprint: 6AAB 544D 3432 D013 776D 3602 ADB6 6B2A D93F 0F93
7:30 a.m.
Anand Capur wrote:
So is our wiki packaged in fedora? Is our account system packaged in
fedora?
It's kinda difficult to see what you are replying to every time you
delete the previous message from your reply...
Both mediawiki (simple) and moinmoin (fedoraproject.org) are packaged
for Fedora. What components make up our complete account system, I don't
know.
Kind regards,
Jeroen van Meeuwen
-kanarip
1:08 p.m.
On Tue, 2007-06-19 at 14:30 +0200, Jeroen van Meeuwen wrote:
Both mediawiki (simple) and moinmoin (fedoraproject.org) are packaged
for Fedora. What components make up our complete account system, I don't
know.
FWIW, a magazine (i.e., a serious publication effort) needs a real CMS.
A wiki just won't do.
Thankfully we have Plone and a growing body of experts, new code, and
about to be experienced users.
- Karsten
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
7:55 a.m.
Once upon a time Tuesday 19 June 2007, Anand Capur wrote:
So is our wiki packaged in fedora? Is our account system packaged in
fedora?
wiki is account system lives in public cvs. the account system is an
exception it is some custom scripts that really are not usefull to anyone
else. but if someone thinks it would be useful they are free to use it.
Dennis
8 a.m.
> So is our wiki packaged in fedora? Is our account system
packaged in
> fedora?
wiki is account system lives in public cvs. the account system is an
exception it is some custom scripts that really are not usefull to anyone
else. but if someone thinks it would be useful they are free to use it.
Dennis
Ok, I'll get it packaged then use it :), where is the Account System?
I read on the wiki that it was on an internal redhat cvs server.
8:10 a.m.
Once upon a time Tuesday 19 June 2007, Anand Capur wrote:
> > So is our wiki packaged in fedora? Is our account system
packaged in
> > fedora?
>
> wiki is account system lives in public cvs. the account system is an
> exception it is some custom scripts that really are not usefull to
> anyone else. but if someone thinks it would be useful they are free to
> use it.
>
> Dennis
Ok, I'll get it packaged then use it :), where is the Account System?
I read on the wiki that it was on an internal redhat cvs server.
http://cvs.fedora.redhat.com/viewcvs/fedora-accounts/?root=fedora
12:46 p.m.
On Mon, Jun 18, 2007 at 12:29:38PM -0500, Mike McGrath wrote:
Anand Capur wrote:
>We are going to be a real online magazine with an ISSN number with the
>possibility of going to a print edition in the future. I have a flash
>based
>magazine reader and many other things that could not run on the wiki.
>We are
>a totally separate idea than FWN.
I saw that, and as for the namespace you need a completely separate
domain? fedoraproject.org/FedoraMagazine/ won't work? Also you'll be
using PHP, please explain more what you'll be doing with php. We are
extremely concerned about php in our environment.
I'm extremely concerned that an official Fedora magazine would require
the proprietary Flash plugin to view.
12:50 p.m.
Chuck Anderson wrote:
On Mon, Jun 18, 2007 at 12:29:38PM -0500, Mike McGrath wrote:
> Anand Capur wrote:
>> We are going to be a real online magazine with an ISSN number with the
>> possibility of going to a print edition in the future. I have a flash
>> based
>> magazine reader and many other things that could not run on the wiki.
>> We are
>> a totally separate idea than FWN.
> I saw that, and as for the namespace you need a completely separate
> domain? fedoraproject.org/FedoraMagazine/ won't work? Also you'll be
> using PHP, please explain more what you'll be doing with php. We are
> extremely concerned about php in our environment.
I'm extremely concerned that an official Fedora magazine would require
the proprietary Flash plugin to view.
Absolutely. I would strongly suggest you avoid flash completely or offer
Ogg video or animated GIF files as alternatives.
Rahul
1:06 p.m.
On 6/18/07, Chuck Anderson <cra(a)wpi.edu> wrote:
On Mon, Jun 18, 2007 at 12:29:38PM -0500, Mike McGrath wrote:
> Anand Capur wrote:
> >We are going to be a real online magazine with an ISSN number with the
> >possibility of going to a print edition in the future. I have a flash
> >based
> >magazine reader and many other things that could not run on the wiki.
> >We are
> >a totally separate idea than FWN.
>
> I saw that, and as for the namespace you need a completely separate
> domain? fedoraproject.org/FedoraMagazine/ won't work? Also you'll be
> using PHP, please explain more what you'll be doing with php. We are
> extremely concerned about php in our environment.
I'm extremely concerned that an official Fedora magazine would require
the proprietary Flash plugin to view.
I would like to add a +1 on this.
Listen I realize that having flash will enhance how it is perceived
and will allow more editorial control on layout. However, it would
seem to undercut the core message of Fedora == Freedom. If you have to
use propietary authoring controls to create that message... you have
weakened the message.
Until gnash (or something equivalnet) is shipped core in Fedora.. I
would be concerned that any official Fedora product should be able to
be used with only a Core product.
--
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"
1:08 p.m.
On Mon, 18 Jun 2007, Stephen John Smoogen wrote:
I would like to add a +1 on this.
Listen I realize that having flash will enhance how it is perceived
and will allow more editorial control on layout. However, it would
seem to undercut the core message of Fedora == Freedom. If you have to
use propietary authoring controls to create that message... you have
weakened the message.
Until gnash (or something equivalnet) is shipped core in Fedora.. I
would be concerned that any official Fedora product should be able to
be used with only a Core product.
+10.
And let's not even START about the section 508 and flash issues.
seriously, friends don't let friends use flash.
-sv
1:26 p.m.
On Mon, 2007-06-18 at 14:08 -0400, Seth Vidal wrote:
On Mon, 18 Jun 2007, Stephen John Smoogen wrote:
> I would like to add a +1 on this.
>
> Listen I realize that having flash will enhance how it is perceived
> and will allow more editorial control on layout. However, it would
> seem to undercut the core message of Fedora == Freedom. If you have to
> use propietary authoring controls to create that message... you have
> weakened the message.
>
> Until gnash (or something equivalnet) is shipped core in Fedora.. I
> would be concerned that any official Fedora product should be able to
> be used with only a Core product.
+10.
And let's not even START about the section 508 and flash issues.
seriously, friends don't let friends use flash.
A lot of what Flash can do can be done in SVG if you have a modern
browser (FF 1.5+, dunno about the status of IE). Recently Nicu Buculei
posted a demonstration web site done entirely in SVG[1]. Not that I'd
really recommend it though, but it shows the power of SVG. The Totem
Mozilla plugin does an excellent job of displaying embedded video as
well.
Even if gnash or swfdec become part of Fedora, they will always be
playing "catch up" with a proprietary standard controlled by a
commercial company.
[1] http://nicubunu.blogspot.com/2007/06/authoring-svg-websites-with-inkscape...
Jeff
6153
days inactive
6157
days old
infrastructure@lists.fedoraproject.org
54 comments
14 participants
participants (14)
-
Anand Capur -
Bart Couvreur -
Chuck Anderson -
Dennis Gilmore -
Gerold -
Jasper, Brandon R CTN2 NSSC BANGOR WA, NSSC Bangor N621 -
Jeffrey Ollie -
Jeroen van Meeuwen -
Karsten Wade -
Mike McGrath -
Nils Breunese -
Rahul Sundaram -
seth vidal -
Stephen John Smoogen