castleproject / home Goto Github PK

Was wondering what you want to do with the following:

http://www.castleproject.org/

Do we want to give it a face lift or move it to a gh wiki?

https://github.com/castleproject/Core/tree/master/docs
https://github.com/castleproject/Windsor/tree/master/docs

This has alot of stuff here, do we intended to maintain it there or do we also want to transition this over to a wiki somewhere? Should we make it all consistent? Are there markdown styling guidelines?

Would be good to clean this up and make it all look consistent.

All docs/projects harmonised in one place. Transparent.

Easy for desktop clr guys to interoperate with azure cloud guys when it comes to contributing. Dont forget our banking compatriates who are "eons" behind.

Logo's everywhere. Complete re-brand of Castle.

Deletion of rogue templated ghpages.

As far as I am aware, some other projects reserve the ProjectOrCompanyName.* namespace prefix (on NuGet) just for themselves, but they allow third-party packages under ProjectOrCompanyName.Contrib.*. See e.g. SpecFlow's 2017 blog article on this.

@castleproject/pmc, does the Castle project have anything similar, i.e. a namespace (both in the sense of a C# namespace and a NuGet package prefix) dedicated to, and reserved for, third-party contributions? If so:

• What is it called?
• Is this documented somewhere?

Castle Core and Windsor master branches are now building off AppVeyor and Travis CI, we no longer need our TeamCity server and Linux agent so I'll be taking a backup and shutting them down today.

I'll redirect http://builds.castleproject.org/ to our github.com organisation page as these services don't really have a good page to link to.

/cc @fir3pho3nixx @alinapopa @blairconrad

• castle-READONLY-SVN-dump
• Castle.DynamicProxy-READONLY
• Castle.Facilities.ActiveRecordIntegration-READONLY
• Castle.ActiveRecord-READONLY
• Castle.Facilities.NHibernateIntegration-READONLY
• Castle.MonoRail3-READONLY
• Castle.Facilities.Wcf-READONLY
• Castle.Windsor-READONLY
• Castle.MonoRail-READONLY
• Castle.Components.Binder-READONLY
• Castle.Core-READONLY
• Castleproject.org-Site-READONLY
• Attic

I've left ActiveRecord and others for now, want to get some consensus around the remaining ones.

Both contributors have been working with the Castle Project over the last 12 months and have contributed significantly. Welcome to the Castle Project team! 🎉

• Dominique Schuppli (@stakx)
• Gavin van der Merwe (@fir3pho3nixx)

Our team page lists 10s of committers who are no longer active as well a Project Management Committee (PMC) that are mostly inactive. The goal here is to establish who wants to continue as an active member and mark those that don't with emeritus status.

• Team page: http://www.castleproject.org/about/team/

The repos on the contrib org haven't been touched in at least 2 years, some even up to 7 years. The concept of "contrib" doesn't make sense now that we have GitHub that provides free infrastructure, while our contrib repo in Subversion was from an era when you couldn't just create your own repos unless you created your own project on something like sf.net.

I couldn't find any real convention people have followed for this type of org, however I want to make it clear what isn't supported without loosing git history, GitHub issues and pull requests, so a single "attic" repo doesn't really work. I've also decided not to use the term attic since I don't believe Castles have attics, so I've followed the naming convention of Rust: https://github.com/rust-lang-deprecated.

This becomes that:

• https://github.com/castleprojectcontrib
• https://github.com/castleproject-deprecated

Today it has become common practice among open source projects to add badges to the README with quick links to nuget, the build server and a discussion channel. Regarding discussions I noticed a reference to a mailing list. May I suggest using Gitter instead? You can easily reserve www.gitter.im/castleproject and then add rooms for Home, Core, Windsor.

Thoughts?