Skip to Content.
Sympa Menu

devel - Re: [sympa-developpers] take the sympa organization back ?

Subject: Developers of Sympa

List archive

Chronological Thread  
  • From: IKEDA Soji <address@concealed>
  • To: Marc Chantreux <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-developpers] take the sympa organization back ?
  • Date: Sat, 26 May 2018 10:27:01 +0900

Marc,

On Fri, 25 May 2018 14:40:01 +0200
Marc Chantreux <address@concealed> wrote:

> Acronyms:
> GH: github
> GHO: github organization
>
> Status:
> open to discussion until: 2018-06-01
> default: apply
>
> hello people,
>
> i created the sympa-community GHO because the sympa one was already taken by
> someone who created a clone back to 2009. I wasn't sure about how successful
> the sympa community github migration will be and at the time i really
> expected
> it to be temporary.
>
> how it seems obvious than:
>
> * sympa-community GHO is the official, succesful gathering of the sympa
> community on github.
> * there is no need to move
> * this old repo should disapear
>
> but @flack never replied to my inviting to join the community and i plane to
> write to github staff about the situation.
>
> what i would like to ask is just to
>
> delete the sympa GHO
> rename the sympa-community GHO to sympa
>
> what do you think?

As I don't know your motivation (it's often unclear in your
proposal), I think out a case long organizaton name is inconvenient.


URL of documentation site <https://sympa-community.github.io/> is a
bit long. However domain part may be customized to preferred name,
for example <https://docs.sympa.org/>, by publishing CNAME record.
Previously GitHub did not support certificates for HTTPS with custom
domain, now there is not such limitaton:
https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

taggart suggested Netlify <https://www.netlify.com> that can host
web contents based on git repo. It has supported HTTPS with custom
domain.

Anyway, at least on documentaton site, long community name does not
matter (name of repository will be still long due to feature).
I want to propose use of custom domain on doc site in some day.

> regards.
> marc

In another post:
> that was the plan:
>
> 1. having a plan A
> 2. collect the agreements and alternative ideas on the list
> 3. ask for whatever we decided on the list to github
> 4. if github can't, goto 2
>
> i'm currently at line 2 but i can make 3 in parallel.

As staff of GitHub help desk are also labors, you would be better
to put questions together, and ask them as less times as possible.


Regards,
-- Soji


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



Archive powered by MHonArc 2.6.19+.

Top of Page