Allow new special characters to profile names
"Aurélio A. Heckert"
aurelio at colivre.coop.br
Fri Feb 7 22:44:07 BRST 2014
Very very nice! Kudos!
I will put some questions only to try to reach the better solution for all.
0 - What is the objective of networks plugin and the network profile?
Will other profile members? With this we can think better on proposals,
usage and contributions.
1 - You really need to add the parent on the path? That means Child11
can't be above Child2 when it is already above Child1. The
sub-communities plugin do not allow multiple parents too, but that must
to be an option some day.
2 - That looks hierarchical, so, that is really a network? Why not call
tree as it really looks like and each branch called "branch"?
3 - Why not to contribute with the sub-communities plugin? We like the
idea to have multiple sub-levels. You will get the nice last
improvements too.
Proposal:
I think the ":" may be a good separator, but "::" no, that is like "//".
(I get it! You was thinking with you nerd brain side ;-])
Hasta!
Aurium
On 07-02-2014 10:45, daniel tygel wrote:
> We're working in the networks plugin, which will add a new profile,
> called Networks.
>
> Since they are hierarchical with arbitrary levels, we are thinking of
> nice ways to display the URLs of the nodes inside each network.
>
> For example: Network has Child1 as a first level child node. And
> Child1 has Child11 as its own child node. Our proposal is that the url
> of the Child11 profile has a "pathway" format, like this:
>
> /network::child1::child11
>
> Today, only "-", ".", "~" and "_" are allowed, but URLs can accept
> ":", "|" and "*" as other valid options.
>
> We are willing to allow these 3 characters ( : | * ) to be used in
> profile urls. Is there any problem if we do a merge-request for that?
>
> Thanks,
>
> daniel and braulio
>
More information about the Noosfero-dev
mailing list