This site has been archived. To learn more about our current products Ibexa Content, Ibexa Experience, Ibexa Commerce head over to the Ibexa Developer Portal

eZ Community » Blogs » share.ez.no team » The share.ez.no team : “We change...

By

The share.ez.no team : “We change the way we work: we want more contact with you.”

Monday 14 May 2012 8:52:22 pm

  • Currently 5 out of 5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

The Share Team is responsible for maintaining the eZ Community portal http://share.ez.no. Until now the team has taken on each task that came along primarily on their own, without help from any other community members, exception to be made of the amazing design contest. This approach is going to change.

Facing an increasing need for care on share.ez.no, as well as on other key platforms powering our community, such as projects.ez.no, the Share Team will now be committed to facilitating and spearheading any tasks e.g. projects coming from within the team and/or the community and help with their great experience of the eZ Community infrastructure management. This means that we will open-up systematically for crowd-help, on all significant projects. This has proven to be very effective, the most visible examples are the Job Board and the Event calendar.

collaboration

Source: Flickr, gogoloopies

The main benefits of this new approach are more collaboration from the community, and also a set timeframe in which these tasks e.g. projects will be running (better predictability, in the end). This will also motivate our own team members, and all volunteering community members who will have many more occasions to learn eZ Publish, hands-on, along with the share.ez.no team experts. We heard that there might even be badges for that... :)

Conclusion: if you want to see new features on our community portal, get in touch with the Share Team (comment here, or drop a post in the dedicated forum). We, the Share Team, will work with you, and provide you with all the tools you would need to accomplish such tasks.

Proudly Developed with from