Different repository for web stuff

[Aleksey Bragin]

	Hi,
how about using a different repository for all web-specific stuff we  
have? Vendor drops of web apps, whole trunk/web, etc. All of these  
are totally unrelated (in terms of repository-internal relations)  
with the actual OS components.

Current situation went from long time ago when there was only one  
repository possible. It's been a long time since we migrated to svn:// 
svn.reactos.org/repostiory/... path, so it's possible now.

rosweb, or web could be a name for a new one.


Comments are welcome.


WBR,
Aleksey Bragin.

[Danny Götte]

Aleksey Bragin wrote:
>   Comments are welcome. 
I support that idea.

[Thomas Bluemel]

I've been wanting this separated for a LONG time. I agree, it has 
nothing to do with ReactOS itself and should deserve it's own separate 
repository.

Thomas

Aleksey Bragin wrote:
>   	Hi,
>  how about using a different repository for all web-specific stuff we  
>  have? Vendor drops of web apps, whole trunk/web, etc. All of these  
>  are totally unrelated (in terms of repository-internal relations)  
>  with the actual OS components.
>  
>  Current situation went from long time ago when there was only one  
>  repository possible. It's been a long time since we migrated to svn:// 
>  svn.reactos.org/repostiory/... path, so it's possible now.
>  
>  rosweb, or web could be a name for a new one.
>  
>  
>  Comments are welcome.
>  
>  
>  WBR,
>  Aleksey Bragin.
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev

[Zachary Gorden]

YES.  It's about damn time we finally separated the web stuff from the OS
itself *cough*.  To be frank, the CMS is more of a separate project entirely
that just happens to be used by the ROS team and has several ROS members
working on it.

[Ged]

How about actually branching it off as a completely separate project and
seeing if it generates any interest?
It might be a good way to both improve the codebase and generate some good
publicity for ReactOS

Ged.

-----Original Message-----
From: ros-dev-bounces(a)reactos.org [mailto:[e-mail]] On
Behalf Of Aleksey Bragin
Sent: 06 April 2009 16:31
To: ReactOS Development List
Subject: [ros-dev] Different repository for web stuff

	Hi,
how about using a different repository for all web-specific stuff we  
have? Vendor drops of web apps, whole trunk/web, etc. All of these  
are totally unrelated (in terms of repository-internal relations)  
with the actual OS components.

Current situation went from long time ago when there was only one  
repository possible. It's been a long time since we migrated to svn:// 
svn.reactos.org/repostiory/... path, so it's possible now.

rosweb, or web could be a name for a new one.


Comments are welcome.


WBR,
Aleksey Bragin.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[Danny Götte]

Ged wrote:
>   How about actually branching it off as a completely
> separate project and
>  seeing if it generates any interest?
>  It might be a good way to both improve the codebase and generate some good
>  publicity for ReactOS 
It doesn't make sense for everything in web/, some things
like RosCMS 
can be developed seperately, but other things like the supportDB are imo 
not that useful for other websites, so they should remain near the 
reactos repo.

[Ged]

Yeah, I was referring to splitting only RosCMS into a standalone project. 
Any addons, bespoke items, forums, etc would be separate to this.

-----Original Message-----
From: ros-dev-bounces(a)reactos.org [mailto:[e-mail]] On
Behalf Of Danny Götte
Sent: 06 April 2009 20:45
To: ReactOS Development List
Subject: Re: [ros-dev] Different repository for web stuff

Ged wrote:
>   How about actually branching it off as a completely
> separate project and
>  seeing if it generates any interest?
>  It might be a good way to both improve the codebase and generate some good
>  publicity for ReactOS 
It doesn't make sense for everything in web/, some things
like RosCMS 
can be developed seperately, but other things like the supportDB are imo 
not that useful for other websites, so they should remain near the 
reactos repo.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

[Aleksey Bragin]

I think Ged means publishing RosCMS as a standalone project  
(releases, news, etc), useful for other people, not moving it to yet  
another repository of course.
At least it could give it more testing, more real usage, and show off  
its advantages over hundreds of other existing CMS.

WBR,
Aleksey Bragin.


On Apr 6, 2009, at 11:45 PM, Danny Götte wrote:

>   Ged wrote:
> >   How about actually branching it off as a
> > completely separate  
> >  project and
> >  seeing if it generates any interest?
> >  It might be a good way to both improve the codebase and generate  
> >  some good
> >  publicity for ReactOS 
>  It doesn't make sense for everything in web/, some
> things like RosCMS
>  can be developed seperately, but other things like the supportDB  
>  are imo
>  not that useful for other websites, so they should remain near the
>  reactos repo.

[Danny Götte]

Aleksey Bragin wrote:
>   I think Ged means publishing RosCMS as a standalone
> project  
>  (releases, news, etc), useful for other people, not moving it to yet  
>  another repository of course.
>  At least it could give it more testing, more real usage, and show off  
>  its advantages over hundreds of other existing CMS.
>
>  WBR,
>  Aleksey Bragin.
>     
I planned already while the development of RosCMS 4, to make it usable 
for other sites. And establish a standalone site for it. Also with 
marketing for ReactOS in mind.

[Aleksey Bragin]

Readonly version of the repository is ready for testing:
svn://svn.reactos.org/web

Paths aren't changed yet (they represent the layout from the main  
repo), and there is an artifact of a few empty revisions in the  
beginning (from 2 to 21), but besides this things are fine.


WBR,
Aleksey Bragin.

On Apr 7, 2009, at 12:03 AM, Aleksey Bragin wrote:

>   I think Ged means publishing RosCMS as a standalone
> project
>  (releases, news, etc), useful for other people, not moving it to yet
>  another repository of course.
>  At least it could give it more testing, more real usage, and show off
>  its advantages over hundreds of other existing CMS.
>
>  WBR,
>  Aleksey Bragin.
>
>
>  On Apr 6, 2009, at 11:45 PM, Danny Götte wrote:
>
> > Ged wrote:
> >> How about actually branching it off as a completely separate
> >> project and
> >> seeing if it generates any interest?
> >> It might be a good way to both improve the codebase and generate
> >> some good
> >> publicity for ReactOS
> > It doesn't make sense for everything in web/, some things like RosCMS
> > can be developed seperately, but other things like the supportDB
> > are imo
> > not that useful for other websites, so they should remain near the
> > reactos repo.

[Alexandru Lovin]

Gentlemen,

I have a question about RosCMS. Is it possible to use it for ANY website
? Let's say an online store. With a forum. And a facility to upload videos
and pictures (think Youtube or Dailymotion but with the ability to upload
static picture galleries as well, with
Lightview<http://www.nickstakenburg.com/projects/lightview/>or
lightbox.js <http://www.huddletogether.com/projects/lightbox/>). And a blog
portion. And a database of downloads, sortable by tags or categories.

I know the ReactOS website already has a forum and blogs. Can the other
features be implemented so that they can be administered from within RosCMS
?

On Tue, Apr 7, 2009 at 7:00 PM, Aleksey Bragin &lt;aleksey(a)reactos.org&gt; wrote:

>   Readonly version of the repository is ready for
> testing:
>  svn://svn.reactos.org/web
>
>  Paths aren't changed yet (they represent the layout from the main
>  repo), and there is an artifact of a few empty revisions in the
>  beginning (from 2 to 21), but besides this things are fine.
>
>
>  WBR,
>  Aleksey Bragin.
>
>  On Apr 7, 2009, at 12:03 AM, Aleksey Bragin wrote:
>
> >   I think Ged means publishing RosCMS as a
> > standalone project
> >  (releases, news, etc), useful for other people, not moving it to yet
> >  another repository of course.
> >  At least it could give it more testing, more real usage, and show off
> >  its advantages over hundreds of other existing CMS.
> >
> >  WBR,
> >  Aleksey Bragin.
> >
> >
> >  On Apr 6, 2009, at 11:45 PM, Danny Götte wrote:
> >
> > > Ged wrote:
> > >> How about actually branching it off as a completely separate
> > >> project and
> > >> seeing if it generates any interest?
> > >> It might be a good way to both improve the codebase and generate
> > >> some good
> > >> publicity for ReactOS
> > > It doesn't make sense for everything in web/, some things like RosCMS
> > > can be developed seperately, but other things like the supportDB
> > > are imo
> > > not that useful for other websites, so they should remain near the
> > > reactos repo. 
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  


-- 
Alex Lovin - www.erasereality.3x.ro

[Danny Götte]

Alexandru Lovin wrote:
>   Gentlemen,
>
>  I have a question about RosCMS. Is it possible to use it for ANY website
>  ? Let's say an online store. With a forum. And a facility to upload videos
>  and pictures (think Youtube or Dailymotion but with the ability to upload
>  static picture galleries as well, with
>  Lightview<http://www.nickstakenburg.com/projects/lightview/>or
>  lightbox.js <http://www.huddletogether.com/projects/lightbox/>). And a blog
>  portion. And a database of downloads, sortable by tags or categories.
>
>  I know the ReactOS website already has a forum and blogs. Can the other
>  features be implemented so that they can be administered from within RosCMS
>  ? 
Forum and Blogs have their own administration, RosCMS just provides some 
plugins for them to use RosCMSs login system instead of their own, so 
that you can use all with only one account.
RosCMS itself just generates static files like .html or .css.

To get more info about RosCMS, you can visit #reactos-web on 
freenode.net or get this discussion to ros-web mailinglist, but you can 
also write me an E-Mail, I don't think that this ML is the right place 
for RosCMS discussions.

[Aleksey Bragin]

I had to do a reimport, because Danny's branch was not included.
Url is the same svn://svn.reactos.org/web
But if someone did a checkout of that repository before the re- 
import, you need to trash it and do a new one.

Currently, those people have write access to the repository:
cfinck - Colin Finck
cwittich - Christoph von Wittich
dgoette - Danny Goete
abragin - Aleksey Bragin
frik85 - Klemens Friedl
gedmurphy - Ged Murphy

Passwords match your main accounts. If someone else needs write  
access, drop me a line.


WBR,
Aleksey Bragin.

On Apr 7, 2009, at 8:00 PM, Aleksey Bragin wrote:

>   Readonly version of the repository is ready for
> testing:
>  svn://svn.reactos.org/web
>
>  Paths aren't changed yet (they represent the layout from the main
>  repo), and there is an artifact of a few empty revisions in the
>  beginning (from 2 to 21), but besides this things are fine.
>
>
>  WBR,
>  Aleksey Bragin.
>
>  On Apr 7, 2009, at 12:03 AM, Aleksey Bragin wrote:
>
> > I think Ged means publishing RosCMS as a standalone project
> > (releases, news, etc), useful for other people, not moving it to yet
> > another repository of course.
> > At least it could give it more testing, more real usage, and show off
> > its advantages over hundreds of other existing CMS.
> >
> > WBR,
> > Aleksey Bragin.
> >
> >
> > On Apr 6, 2009, at 11:45 PM, Danny Götte wrote:
> >
> >> Ged wrote:
> >>> How about actually branching it off as a completely separate
> >>> project and
> >>> seeing if it generates any interest?
> >>> It might be a good way to both improve the codebase and generate
> >>> some good
> >>> publicity for ReactOS
> >> It doesn't make sense for everything in web/, some things like  
> >> RosCMS
> >> can be developed seperately, but other things like the supportDB
> >> are imo
> >> not that useful for other websites, so they should remain near the
> >> reactos repo.

[King InuYasha]

On Tue, Apr 7, 2009 at 2:53 PM, Aleksey Bragin <aleksey(a)reactos.org> wrote:

>   I had to do a reimport, because Danny's branch was
> not included.
>  Url is the same svn://svn.reactos.org/web
>  But if someone did a checkout of that repository before the re-
>  import, you need to trash it and do a new one.
>
>  Currently, those people have write access to the repository:
>  cfinck - Colin Finck
>  cwittich - Christoph von Wittich
>  dgoette - Danny Goete
>  abragin - Aleksey Bragin
>  frik85 - Klemens Friedl
>  gedmurphy - Ged Murphy
>
>  Passwords match your main accounts. If someone else needs write
>  access, drop me a line.
>
>
>  WBR,
>  Aleksey Bragin.
>
>  On Apr 7, 2009, at 8:00 PM, Aleksey Bragin wrote:
>
> >   Readonly version of the repository is ready for
> > testing:
> >  svn://svn.reactos.org/web
> >
> >  Paths aren't changed yet (they represent the layout from the main
> >  repo), and there is an artifact of a few empty revisions in the
> >  beginning (from 2 to 21), but besides this things are fine.
> >
> >
> >  WBR,
> >  Aleksey Bragin.
> >
> >  On Apr 7, 2009, at 12:03 AM, Aleksey Bragin wrote:
> >
> > > I think Ged means publishing RosCMS as a standalone project
> > > (releases, news, etc), useful for other people, not moving it to yet
> > > another repository of course.
> > > At least it could give it more testing, more real usage, and show off
> > > its advantages over hundreds of other existing CMS.
> > >
> > > WBR,
> > > Aleksey Bragin.
> > >
> > >
> > > On Apr 6, 2009, at 11:45 PM, Danny Götte wrote:
> > >
> > >> Ged wrote:
> > >>> How about actually branching it off as a completely separate
> > >>> project and
> > >>> seeing if it generates any interest?
> > >>> It might be a good way to both improve the codebase and generate
> > >>> some good
> > >>> publicity for ReactOS
> > >> It doesn't make sense for everything in web/, some things like
> > >> RosCMS
> > >> can be developed seperately, but other things like the supportDB
> > >> are imo
> > >> not that useful for other websites, so they should remain near the
> > >> reactos repo. 
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  

RosCMS seems to basically be an SSO (single-sign-on) framework rather than a
complete CMS. Still, I think RosCMS would get more love spun off as a
separate project rather than being needlessly huggled to ReactOS.

[Zachary Gorden]

All of the content publishing, newsletters, pages, etc, are handled by CMS
code written by the web team.  It just happens to have also been modified to
integrate nicely with other things like the forum and blogging system.