Quote:

When it is defined what makes a site considered to be "official", and why it should be like this and how it's planned to be succesfully achieved.

Then it would be easier to make the differentiation you mention.

Thank you Kris and David for the nomination. I think the current design group counts with very skilled members and if they make public notice of the projects they work on and I am available at the moment I'd be happy to work with them.

Right now, I need a little rest, a small vacation to clear my mind up and be able to focus completely on theme and template creation but I need this rest now to gather new energies.

I'll be a supporter of the design team but not as member at the moment, not necessarily you have to be member of a team to be able to contribute to the works the teams are doing; leaving open the possibility of joining in a future.

If a leader is being voted for, I think Incama or StudioC are the ones with the most specialized skills for this.

A site with a forum created by the past core developers where a set of people were in charge of analyzing all the current xoops.org site and retrieving from all the past forum threads feedback on how it was thought to make XOOPS better, arriving to conclusions with all that information to make the structure of the network of the main XOOPS sites, once the structure of sites were ready they were to be opened to the community so team formation could be made. That approach did not work, so plans changed and it was concluded that the opensource perspective I mention in the above post would be best as it would leave everything open to the community. From there it was left to my understanding that the best approach is for core developers to take care fundamentally of the core and bringing to success to the XOOPS software. Other areas left under control of the community and this way create a balance.

Ok, I will make a report of the status of addons, how it has been defined until the moment and it's objectives.

I want to make note to clear the concept, when I said "community managed site", I mean that it (XOOPS Addons) has been defined as an independent site managed by a community member(s) who's responsibility is to provide the interactive space for the community, it's management external from the main centralized XOOPS management planned by the lead core developer.

The main centralized XOOPS management being focused to take care of the core and progress of XOOPS software. While the other areas being external and independently owned by a community member who shows a leadership in providing this space (xoops "information" site) lets free for the decisions to be taken by community members without the project leaders to be directly involved. That is sort of the ideology that was being applied until now. That was why XOOPS was divided in a network of sites, each independently owned under an open source environment. If I remember well, only 2 sites were to be considered "official" and managed by the project leaders: xoops.org : the product site , and the documentation, and a (possible 3rd site) core dev site if it was needed a space other than the one sourceforge provides; all else was left in hands of the community independently owned by those who stand out as leaders. The foundation taking care of supporting the XOOPS project and community initiatives. Everything being interrrelated.

That was what has been defined. And I'll place the status of XOOPS Addons under this perspective as it's the one I've known until now, and leave the decision for the project leader, if this perspective of open source will continue or to establish a new perspective of how the different XOOPS sites will be handled, mainly for the ones considered in the XOOPS site subdivision.

A definition of XOOPS objectives of the root of the project, XOOPS objectives as a community and how open source will be applied to the whole movement, would be good to ensure that a fragile Babel Tower is not built. I get a feeling that "+1" or "unconstructive negativism", won't build anything solid when the foundation of what XOOPS is and how we want it to work is not clearly defined, so it feels like we are voting or judging blindly. Please don't take me wrong, I don't mean to be negative with this, it's an observation done looking after something positive.

There's something in the order things are being done that doesn't seem right to me. How can I tell someone: "I'm going on an excursion, join me", I get a group, then they ask me "What are we going to do?" and I say "We are going to jump off a mountain in a parachute" ... some of them might not think that's too cool. In my opinion the happening of events are happening too rapid. It's been barely 2 days and I think a more carefull analysis is needed and do the steps in order of events. First the manifest (framework - roadmap thing), then the expressing of the plans and desired tasks, then team formation, but not all at the same time as it may cause confusion.

Hi phppp,

Regarding the XOOPS module repository, specifically point #3 = maintain XOOPS module repository. The site is being built from the notes taken at mxo, It was understood to me that the site although a sub-official site, would be or is, I don't have it clear now, a community managed site under the supervision of an admin or group of admins that leader it. I've been in charge of leaving the structure finished and have given it's administration to David and Vaughan as main admin supervisors in charge of it's inauguration and making plans for the team structure and follow up on it's organization.

I've got a meeting pending with the administrators to take final decisions on the content structure and finish building the site and leave them in charge.

Please advise me what I should do with the change of plans, and who I should I hand everything to, to let them finish what was started, if it is still in mind of using the work done of the site setup. Or what you suggest the plans to be?

Thank you,
Ana

I am very aware of your closeness you had to the perspective and plans Skalpa had with taking XOOPS to 2.3/2.4. I appreciate your nomination to the team and really hope you can bring into the future plans of XOOPS what you learned from him and your ideas.

Mucha suerte! Espero verte en el equipo!
[size=x-small](Good luck! Hope to see you in the core team!)[/size]

I have received a message from JAVesey about what I have posted, instead of answering by PM I'll answer here in case someone else has the same concerns.

I know this post I put is ahead in time, but is due more to because the whole ground we have been standing on has shifted and I can't help feeling a certain nervousness about the future code of XOOPS. Most of you are happy forming teams and there has been great activity with team formation and I think that's great that the XOOPS community unity is being worked on and the positive interest everyone is showing. I am just as positive only maybe not as happy.

I'll continue being a positive member of XOOPS as it's being shown that the XOOPS project will remain one under the same name. I'll also keep my dedication to elaborating themes and contributing to design work projects proposed by the core team or design team. I may not be joining any team right now but that doesn't mean I won't contribute with the same dedication a team member would.

During the past months I've been very involved making part of the restructuring of xoops, assisting the finalization of the addons site on a more official level and on a personal level creating the xoopswiki and xoopsdemo. It's been alot of work and now that all 3 of these sites are close to being inaugurated, I am very happy to have made part in their creation and being able to give them to the XOOPS community. Each site has an excellent set of admins whom are prepared to receive the working teams.

My dedication to XOOPS will be now for themes and templates and I am happy to have gained once again the free time to continue my design studies since the making of those three sites were really absorbing me.

Thank you JAVesey for your concerns and thanks to all the XOOPS community members for keeping the XOOPS project unified.

PS. I'll be bumping my smarty code concerns soon, when the new community site opens

I want to know if this:



will be compatible with the change XOOPS will have? This was supposed to be the starting point of the code evolving into the XOOPS 2.4 that will no longer exist.

So will all the new xo variables shown in the above image and ones like < {xoImgUrl} >, < {xoAppUrl} >, $theme_name continue in the code? Also will template overriding still exist? Since a change in this would imply a radical change in the themes and templates we make.

Burning, I give you a big applause for what you have done until now, for your intentions...and it would be nice of you continue.

Thank you for the spirit.

You have made citations to a post that was edited by the poster himself...that makes me think that within him there is a truth hiding besides the hate he might feel for xoops... a person who recognized the harm he was doing with his bad feelings and deleted his post...

Do what you do for the love and dedication you have for knowledge and giving other people what you know.

Thank you for everything.

I think you might need to update your theme to be able to display the blocks below module content.
< click here to see a quick how to >

or you can make a comparison and add what's missing comparing your theme with the default theme that's packaged with XOOPS 2.0.16 or this other updated theme.html. Don't forget the new styles for the bottom blocks.