Ivan Habunek | 1 Jun 14:42 2012
Picon

Re: Logging web sites

Joe Schaefer suggested on JIRA [1] to have the site contents in pure
Textile markup instead of Django templates as it is now. The benefit
of this is that it would be somewhat simpler to write contents (no
need for the template boilerplate).

Personally I'm somewhat inclined to leave it as it is now since it's
more flexible and the boilerplate is really not that bad.

The current contents are located at [2].
I will eventually change the ".twig" extension to something else since
we're not using Twig any more.

To illustrate the point further, some projects, like Esme [3], have
something similar, but with Markdown instead of Textile.

What do you think?

Regards,
Ivan

[1] http://s.apache.org/HGr
[2] http://svn.apache.org/repos/asf/logging/site/branches/cms/trunk/content/
[3] http://svn.apache.org/repos/asf/esme/site/trunk/content/

On 31 May 2012 13:44, Ivan Habunek <ivan.habunek <at> gmail.com> wrote:
> On 31 May 2012 12:23, Ralph Goers <rgoers <at> apache.org> wrote:
>> My understanding is if you want to use their system we can use their web UI to edit stuff and we don't really
have to do anything.
>
> We have to at least adapt view.pm and path.pm, like Joe Schaefer said.
(Continue reading)

Ralph Goers | 1 Jun 17:55 2012

Re: svn commit: r1345182 - in /logging/site/branches/cms/trunk: content/ content/js/ templates/

Have you found out how to test this yet?  How are you able to preview the changes you've made?

Ralph

On Jun 1, 2012, at 6:58 AM, ihabunek <at> apache.org wrote:

> Author: ihabunek
> Date: Fri Jun  1 13:58:06 2012
> New Revision: 1345182
> 
> URL: http://svn.apache.org/viewvc?rev=1345182&view=rev
> Log:
> Minor improvemetns to templates. Added support for external links.
> 
> Added:
>    logging/site/branches/cms/trunk/content/js/site.js
> Modified:
>    logging/site/branches/cms/trunk/content/charter.twig
>    logging/site/branches/cms/trunk/content/guidelines.twig
>    logging/site/branches/cms/trunk/content/index.twig
>    logging/site/branches/cms/trunk/content/mailing-lists.twig
>    logging/site/branches/cms/trunk/content/privacy-policy.twig
>    logging/site/branches/cms/trunk/content/team-list.twig
>    logging/site/branches/cms/trunk/templates/footer.html
>    logging/site/branches/cms/trunk/templates/navbar.html
>    logging/site/branches/cms/trunk/templates/page.html
> 
> Modified: logging/site/branches/cms/trunk/content/charter.twig
> URL: http://svn.apache.org/viewvc/logging/site/branches/cms/trunk/content/charter.twig?rev=1345182&r1=1345181&r2=1345182&view=diff
> ==============================================================================
(Continue reading)

Ivan Habunek | 1 Jun 18:00 2012
Picon

Re: svn commit: r1345182 - in /logging/site/branches/cms/trunk: content/ content/js/ templates/

On 1 June 2012 17:55, Ralph Goers <ralph.goers <at> dslextreme.com> wrote:
> Have you found out how to test this yet?  How are you able to preview the changes you've made?

Not yet. I asked on the JIRA issue, but no reply so far. I'll bump the topic.

Regards,
Ivan

Ralph Goers | 4 Jun 06:58 2012

Re: Logging web sites

Ivan, can you poke Infra again and see if you can get them to complete this?

Ralph

On Jun 1, 2012, at 5:42 AM, Ivan Habunek wrote:

> Joe Schaefer suggested on JIRA [1] to have the site contents in pure
> Textile markup instead of Django templates as it is now. The benefit
> of this is that it would be somewhat simpler to write contents (no
> need for the template boilerplate).
> 
> Personally I'm somewhat inclined to leave it as it is now since it's
> more flexible and the boilerplate is really not that bad.
> 
> The current contents are located at [2].
> I will eventually change the ".twig" extension to something else since
> we're not using Twig any more.
> 
> To illustrate the point further, some projects, like Esme [3], have
> something similar, but with Markdown instead of Textile.
> 
> What do you think?
> 
> Regards,
> Ivan
> 
> [1] http://s.apache.org/HGr
> [2] http://svn.apache.org/repos/asf/logging/site/branches/cms/trunk/content/
> [3] http://svn.apache.org/repos/asf/esme/site/trunk/content/
> 
(Continue reading)

Ralph Goers | 7 Jun 02:36 2012

Re: Logging web sites



Ralph



On Jun 1, 2012, at 5:42 AM, Ivan Habunek wrote:

Joe Schaefer suggested on JIRA [1] to have the site contents in pure
Textile markup instead of Django templates as it is now. The benefit
of this is that it would be somewhat simpler to write contents (no
need for the template boilerplate).

Personally I'm somewhat inclined to leave it as it is now since it's
more flexible and the boilerplate is really not that bad.

The current contents are located at [2].
I will eventually change the ".twig" extension to something else since
we're not using Twig any more.

To illustrate the point further, some projects, like Esme [3], have
something similar, but with Markdown instead of Textile.

What do you think?

Regards,
Ivan

[1] http://s.apache.org/HGr
[2] http://svn.apache.org/repos/asf/logging/site/branches/cms/trunk/content/
[3] http://svn.apache.org/repos/asf/esme/site/trunk/content/

On 31 May 2012 13:44, Ivan Habunek <ivan.habunek <at> gmail.com> wrote:
On 31 May 2012 12:23, Ralph Goers <rgoers <at> apache.org> wrote:
My understanding is if you want to use their system we can use their web UI to edit stuff and we don't really have to do anything.

We have to at least adapt view.pm and path.pm, like Joe Schaefer said.
By default they are configured to process only *.mdtext files. I'm
working on it.

Whatever you do, you can just use the area I already created which is documented in the Jira issue.

OK, I will use the /site/branches/cms/trunk/ folder.

Regards,
Ivan

Ralph Goers | 7 Jun 02:47 2012

Re: Logging web sites

And I have to say I very much like being able to edit the main site using the webui.  See https://blogs.apache.org/infra/entry/the_asf_cms

Ralph

On Jun 6, 2012, at 5:36 PM, Ralph Goers wrote:



Ralph



On Jun 1, 2012, at 5:42 AM, Ivan Habunek wrote:

Joe Schaefer suggested on JIRA [1] to have the site contents in pure
Textile markup instead of Django templates as it is now. The benefit
of this is that it would be somewhat simpler to write contents (no
need for the template boilerplate).

Personally I'm somewhat inclined to leave it as it is now since it's
more flexible and the boilerplate is really not that bad.

The current contents are located at [2].
I will eventually change the ".twig" extension to something else since
we're not using Twig any more.

To illustrate the point further, some projects, like Esme [3], have
something similar, but with Markdown instead of Textile.

What do you think?

Regards,
Ivan

[1] http://s.apache.org/HGr
[2] http://svn.apache.org/repos/asf/logging/site/branches/cms/trunk/content/
[3] http://svn.apache.org/repos/asf/esme/site/trunk/content/

On 31 May 2012 13:44, Ivan Habunek <ivan.habunek <at> gmail.com> wrote:
On 31 May 2012 12:23, Ralph Goers <rgoers <at> apache.org> wrote:
My understanding is if you want to use their system we can use their web UI to edit stuff and we don't really have to do anything.

We have to at least adapt view.pm and path.pm, like Joe Schaefer said.
By default they are configured to process only *.mdtext files. I'm
working on it.

Whatever you do, you can just use the area I already created which is documented in the Jira issue.

OK, I will use the /site/branches/cms/trunk/ folder.

Regards,
Ivan


Christian Grobmeier | 7 Jun 07:28 2012
Picon

Re: Logging web sites

Cool.

No we have to deal out how to deploy pages.

Thanks Ralph + Ivan for the hard work so far!

On Thu, Jun 7, 2012 at 2:47 AM, Ralph Goers <ralph.goers <at> dslextreme.com> wrote:
> And I have to say I very much like being able to edit the main site using
> the webui.  See https://blogs.apache.org/infra/entry/the_asf_cms
>
> Ralph
>
> On Jun 6, 2012, at 5:36 PM, Ralph Goers wrote:
>
>
> http://loggingtest.staging.apache.org/index.html is up.
>
> Ralph
>
>
>
> On Jun 1, 2012, at 5:42 AM, Ivan Habunek wrote:
>
> Joe Schaefer suggested on JIRA [1] to have the site contents in pure
> Textile markup instead of Django templates as it is now. The benefit
> of this is that it would be somewhat simpler to write contents (no
> need for the template boilerplate).
>
> Personally I'm somewhat inclined to leave it as it is now since it's
> more flexible and the boilerplate is really not that bad.
>
> The current contents are located at [2].
> I will eventually change the ".twig" extension to something else since
> we're not using Twig any more.
>
> To illustrate the point further, some projects, like Esme [3], have
> something similar, but with Markdown instead of Textile.
>
> What do you think?
>
> Regards,
> Ivan
>
> [1] http://s.apache.org/HGr
> [2] http://svn.apache.org/repos/asf/logging/site/branches/cms/trunk/content/
> [3] http://svn.apache.org/repos/asf/esme/site/trunk/content/
>
> On 31 May 2012 13:44, Ivan Habunek <ivan.habunek <at> gmail.com> wrote:
>
> On 31 May 2012 12:23, Ralph Goers <rgoers <at> apache.org> wrote:
>
> My understanding is if you want to use their system we can use their web UI
> to edit stuff and we don't really have to do anything.
>
>
> We have to at least adapt view.pm and path.pm, like Joe Schaefer said.
>
> By default they are configured to process only *.mdtext files. I'm
>
> working on it.
>
>
> Whatever you do, you can just use the area I already created which is
> documented in the Jira issue.
>
>
> OK, I will use the /site/branches/cms/trunk/ folder.
>
>
> Regards,
>
> Ivan
>
>
>

--

-- 
http://www.grobmeier.de
https://www.timeandbill.de

Christian Grobmeier | 8 Jun 09:04 2012
Picon

Mailinglist Moderators

I am curious if we have moderators on our mailinglists and who they are?
Any ideas how to find out?

--

-- 
http://www.grobmeier.de
https://www.timeandbill.de

Ivan Habunek | 8 Jun 11:04 2012
Picon

Re: Mailinglist Moderators

On 8 June 2012 09:04, Christian Grobmeier <grobmeier <at> gmail.com> wrote:
> I am curious if we have moderators on our mailinglists and who they are?
> Any ideas how to find out?

I asked infra on IRC, the soulution is to ask one of them. I asked:

general <at> logging:
- carnold at apache

private <at> logging:
- carnold at apache
- scott.deboy at gmail

They noted that we should have at least 2 mods for each list.

So, who wants to be mod? :-)

Regards,
Ivan

Ralph Goers | 8 Jun 12:57 2012
Picon

Re: Mailinglist Moderators

I'll volunteer for both. I think it would be good to have at least one more too.

Ralph

On Jun 8, 2012, at 2:04 AM, Ivan Habunek <ivan.habunek <at> gmail.com> wrote:

> On 8 June 2012 09:04, Christian Grobmeier <grobmeier <at> gmail.com> wrote:
>> I am curious if we have moderators on our mailinglists and who they are?
>> Any ideas how to find out?
> 
> I asked infra on IRC, the soulution is to ask one of them. I asked:
> 
> general <at> logging:
> - carnold at apache
> 
> private <at> logging:
> - carnold at apache
> - scott.deboy at gmail
> 
> They noted that we should have at least 2 mods for each list.
> 
> So, who wants to be mod? :-)
> 
> Regards,
> Ivan


Gmane