CLOSING DATE 25 MARCH

[masterchief]

Just letting everyone know that the closing date for papers to be in a reasonable condition for review is approaching. After the 25 March we will be starting to move topics around for review - so make sure you get your 2c worth of opinion in on your favourite topics.

Please don't panic if you see threads being merged and such - it's just to help us process what I think is a fantastic response to this new initiative. Also don't be discouraged if your paper or idea doesn't get picked for 1.6, it might just make a later release or we might run with the idea but in a different way ... we'll see what happens.

1.6 is planned to be made up of a small number of large changes (and before you ask, yes, ACL is one of them) and "a lot" of little things (we'll see how much we can squeeze in while we are tearing our hair out trying to make the ACL work). Time frame is currently unknown but we'd like to keep it less than a four month cycle if at all possible (shorter would be better if we can pull it off).

Overall I'd like to take this opportunity to thank everyone who has responded for getting behind us on this. It's pretty exciting for us to be looking at actually adding new stuff again rather than just fixing things.

[willebil]

Let me second Andrew here, the feedback and discussion going on here is very inspiring, even when it is that much as it is now ;-)

[Stasys]

Maybe it should be sticked on top?

[newart]

Today is the 25th of march... are you closing the reply button in the forum? Are you stopping other new contributions in the forum? What's going on? May we continue to...

[willebil]

We are currently scanning all posts. So far we identified 115 white papers. Posts that refer to the same issue are merged if possible, and then we try to determine what will be the focus for 1.6. We will send out more information when we have ordered all the incoming information (bit overwhelming, but we're happy with that).

We are not going to close down this section, people can go on with writing down proposals and discuss them. Please keep in mind that we expect white papers here, and not one liners because we consider those as feature requests.

Hope this answers your questions.

[cutie_tech123]

Are you closing your reply button?

Mod note: Removed self-promotion.

[newart]

well, about "CLOSING DATE 25 MARCH" ? Today is the 15th of april.

[masterchief]

well, about "CLOSING DATE 25 MARCH" ? Today is the 15th of april.

Let's not beat around the bush. The question you are really asking is "is there any news?" :P

We've got a *very* big spreadsheet, and a heap of people have scored papers and made recommendations etc (takes each person about 4-5 hours to do all the papers). We are up to the point of looking at what's definitely "in" and what's definitely "out" and then we embark on the process of what to do with the bit in between. No surprises for what the number one thing will be

[newart]

very well and thank you vm for yr reply - we have a good white paper list to view

[Scrat4immer]

So far so good
Got any news for us? It's been a while now

greetz
Scrat4immer

[newart]

latest news on http://developer.joomla.org/

[Toon-c]

latest news on http://developer.joomla.org/

ok , so we contribute with comments over there ..
no more ideas accepted now ? (sorry I'm new in here and want to contribute ..)

thanks for answering.
Toon.

[mergen]

What's the time frame for 1.6 release? Even a very rough and very safe date or estimate will be fine.

We want to know if we should develop an extension that MAY get addressed in 1.6.

BTW, I did search for information on this, I just did not find anything in nearly 15/20min of search

Thanks

[newart]

http://joomlacode.org/gf/download/frsre ... la_1.6.pdf

http://vimeo.com/5516584

[feldon27]

I'm checking out the video and PDF. Hope they're linked on Developer.Joomla.org soon.

[newart]

I'm checking out the video and PDF. Hope they're linked on Developer.Joomla.org soon.

as far as I know it isn't up to now

[nickweavers]

I grabbed a copy of Joomla 1.6 alpha from svn and was wondering if there is or will be a forum for feedback? If there is and I have missed it, my apologies for spamming this one and please feel free to move this to its rightful home.

Like all of us, I was eager to see how the new ACL control would work and how intuitively it would be presented. This was my experience so far:

I wanted to create a group called employees for a website to be used as a front and back office for a company. The employees parent is the group registered. Under employees I want to make different menus visible to different classes of employees so I created subgroups of regular (who should for instance be able to fill in time sheets, and availability sheets), office (for office admin who will book regular employees who are available onto jobs) and manager (for managers who would want visibility of what is going on via reports, and to be able to register employees as regular, office or manager). The first problem I got was that it said there was already a group called manager, so it looks like the group names have to be unique regardless of whether the are subgroups, which is not a natural fit with the real world. A bit like a programming language with no variable scoping. Can that easily be changed?

Next I created a new module called regular for one of the menus I wanted to present to the group called regular (offering time sheets and availability forms), but I could not figure out how to restrict a menu to be shown to that group since it only seemed to allow me to specify an acl level. Surely the acl level should be used in conjunction with a group to grant a particular level of access by people in that group to whatever object you are classifying? Could be I am suffering paradigm misalignment here so forgive me if I don't "get it" and please put me straight.

The next question I have is, if I install my own custom component, will I also be able to classify access to that with a group and acl? (I know I'm jumping the gun here and should really have just created a small dummy component install zip to try it, but it would be nice to know).

Thanks to whoever is listening, and all your hard work is really appreciated. Lets go kill us a Drupal! Lol

Nick

PS. I'm using TortoiseSVN and wondered if anyone could tell me how to configure it so that I exclude the installation subdirectory so that I don't have to keep deleting it. (Am I running any risk of missing anything new being set up if I don't periodically run this, like a new database table or table column for example?)

[nickweavers]

Should have watched the video posted by @newart. Things are much clearer to me now on the ACL/groups/users relationships.

Thanks for posting that link @newart.