Developers of Sympa

[Olivier Lumineau <address@concealed>]

Le 15/07/2019 à 08:45, Stefan Hornburg (Racke) a écrit :

On 7/14/19 7:21 AM, Stefan Hornburg (Racke) wrote:

On 7/10/19 9:45 AM, IKEDA Soji wrote:

On Wed, 10 Jul 2019 06:08:23 +0200
"Stefan Hornburg (Racke)" <address@concealed> wrote:

On 7/10/19 5:06 AM, IKEDA Soji wrote:

Hi again,

I edited navbar to redirect menu items to the original documentation
site.  Contents converted from MD to DokuWiki are never tought.

We should examine about new site with enough time, I think.
Until we would do, we'd be better to introduce and use GitHub sites.

Could you please place robots.txt at the top of www.sympa.org site?
I couldn't do it.

robots.txt:
```
User-Agent: *
Disallow: /community
Disallow: /faq
Disallow: /manual
```

Thanks much.

Regards,
-- Soji

Hello Soji,

to be honest the GH pages has drawbacks as well (layout, no search), so I would like
to give the sympa.org a try.

* I have planned to update layout of GitHub Page, but it was not my
  priority.  Of course anyone may do it.

* I added search form on the site. See https://sympa-community.github.io/

Ok, it's all settled.

In order to do that, we need access to the server in a reasonable time frame, so we
can evaluate the setup there and put the stuff into a Git repository.

If that doesn't go to happen soon, I support Soji's request and will try to find the
time to build a reasonable web site based on the community staff. It isn't complicated
to convert Markdown documents into a reasonable static web site and add search
functions.

Markdent (https://metacpan.org/pod/Markdent) is a nice module for this task.

At least it will work better than privately-crafted parser.

                                 *

FYI: This morning a issue was submitted:

  https://github.com/sympa-community/sympa/issues/687

Duplicate contents matter with users and community.
(NOTE: Search engines pick both content either we wish or not.)
Especially, broken content matters.

If we publish information including documentation, we have to take
care not making users confused.  

That's why I propose to put robots.txt hiding probablly incomplete
content.


Regards,

-- Soji

OK, a week has gone by. There is no answer from Olivier and David is out indefinitely,
so I'm supporting the robots.txt proposal.

I'll add the Github pages parsing task to my TODO list, but before that I'll produce
new Sympa packages for buster and stretch and also fixing the Ansible project.

Regards
           Racke

Hello,

in case Olivier doesn't respond soon, I'll try the https://www.dokuwiki.org/plugin:htmlmetatags plugin
to keep sympa.org content out of the search engines.

Regards
        Racke

Hi,
I put the robots.txt.
Otherwise I'm sorry I didn't answer earlier, but I can't devote much time to the Sympa project.

I'll see to move the machines so you can access them. That said, I don't know if it will be effective before the end of August because I will be going on holiday soon for 4 weeks.

When it will be ok, about the site, I think it would be interesting to look at what Etienne has done to get started in a good way to transcribe the content of github on www.sympa.org .

Have a good day

Olivier

Regards
         Racke

On Wed, 10 Jul 2019 11:12:19 +0900
IKEDA Soji <address@concealed> wrote:

Hi Olivier,

Links with teletype text are broken (used frequently in the
document).  See attached screen shot.

For the present, could you please change the links in menu to the
pages in sympa-community.github.com?  It looks required to be
checked carefully before it will be available enough.

Or, as I have been telling, it would be better to assign a new CNAME
record to GitHub Pages site:
  https://help.github.com/en/articles/setting-up-a-custom-subdomain

It's easy, and we no longer will worry about duplicate contents.


Regards,
-- Soji


On Mon, 17 Jun 2019 12:48:18 +0200
David Verdin <address@concealed> wrote:

Dear all,

According to what I said a few months ago, our web designer worked on 
the Sympa web site and reached three goals:

1- Setting a new skin with the new, community-validated logo,

2- Pluging the site to Sympa community: the manual in the Sympa web site 
is now directly generated from the Markdown pages in 
https://github.com/sympa-community/gpldoc

3- Removing federated login (note that you will need to create 
credentials on the new web site, and we'll need to designate people with 
admin rights on the wiki.


I have a basic agreement to move the server to an area where people from 
the community would get administrative rights. I just lack a way to 
officialize the fact that people accessing the esrver would not use it 
to bad ends, such as stealing personal data, sending spam and such. Do 
you have any idea about how to do this? I'd like to harvest consent from 
future admins about theis engagement to good behaviour. Nothing too formal.

Maybe you did this someplace else. If yes, any feedback is welcome.

In the meantime, enjoy: https://www.sympa.org/index

Regards,

David

-- 

"Mieux vaut viser la perfection et la rater que viser la médiocrité et l'atteindre."
- Francis Blanche

-- 
株式会社 コンバージョン
ITソリューション部 システムソリューション1グループ 池田荘児
〒140-0014 東京都品川区大井1-49-15 アクセス大井町ビル4F
e-mail address@concealed  TEL 03-6429-2880
https://www.conversion.co.jp/

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.

--
Olivier LUMINEAU Services Numériques Collaboratifs +33 2 23 23 69 05  263 av du gral Leclerc 35042 RENNES www.renater.fr

---