Adium Website needs an update

[- Neustradamus -]

Dear all,

I think that the website needs an update!

ML is not updated: http://adium.im/pipermail/commits_adium.im/

I am very happy to see a lot of changes on GitHub (Good job Asher) but badly people do not know where is the current sourcecode...
- https://github.com/adium
- https://github.com/adium/adium
- https://github.com/adium/adium/commits/adium-1.5.11.asher.1011fix
- https://github.com/adium/adium/issues (bugtracker)
- https://github.com/adium/adium/pulls

Time to remove the old trac, we are in 2020.

If you want an hosted solution, please use GitLab.

Do not forget to update, Pidgin has a 2.14.1 version now.

New version soon?
- https://github.com/adium/adium/issues/2

I search the Adium .SVG logo:
- https://github.com/adium/adium/issues/3

Add a new website here:
- https://github.com/adium

Thanks in advance.

Regards,

Neustradamus

[Asher Haig]

> On Jun 15, 2020, at 8:57 PM, - Neustradamus - <neustr...@hotmail.com> wrote:
>
> Dear all,
>
> I think that the website needs an update!

Agreed, but what do we want that to mean, and who wants to take charge of it?

I think this gets at a larger question: what role should Adium play at this point?

I think that the combination of accumulated work, bit rot, and the GPL have converged so that it is difficult for people to commit time to writing innovative code that gets trapped in the GPL. This could probably be solved by coming up with a model for creating non-GPL (BSD or whatever) licensed libraries for components that could then be dual-licensed for inclusion in the GPL Adium, but it would need some planning (plus community agreement helps).

>
> ML is not updated: http://adium.im/pipermail/commits_adium.im/

This must be set up in relation to the Hg repo, which is not currently being treated as the primary repo (although all actions taken thus far could be merged back into Hg if ultimately desired).

>
> I am very happy to see a lot of changes on GitHub (Good job Asher) but badly people do not know where is the current sourcecode...

Agreed. And there is not a current release, either. This was to be fixed a while back, but my focus got derailed.

> - https://github.com/adium

This is the org main page.

> - https://github.com/adium/adium

This is the main repo, which needs to have master updated once things are in order (see below). I had done this previously but then we determined bc current master doesn’t share commits with current branch that this had caused problems, so I reverted.

> - https://github.com/adium/adium/commits/adium-1.5.11.asher.1011fix

This is the working branch ATM. I was working on getting things up to date, then we ran into some pre-10.12 compatibility issues and then I got entirely derailed by separate job requirements.

I’ve dipped in here and there since to try to get things back in order, but haven’t had a chance to focus yet.

I’m going to try to clean things up a bit now so that we can clarify and have a functional branch.

> - https://github.com/adium/adium/issues (bugtracker)

There is some confusion / ambiguity about the Github bugtracker vs Trac and/or getting things updated/transferred. I think the decision was tentatively to use the Github tracker as a way to decide which issues to migrate, but this wasn’t a strong conclusion.

> - https://github.com/adium/adium/pulls

This is where pull requests are listed from non-adium users who have made changes to a fork and want the changes included.

> Time to remove the old trac, we are in 2020.

I think this is mostly a question of how to handle migrating old issues (and which ones).

> If you want an hosted solution, please use GitLab.

Not sure what you are suggesting here?

> Do not forget to update, Pidgin has a 2.14.1 version now.

I guess that would be my responsibility. I will look into it.

>
> New version soon?
> - https://github.com/adium/adium/issues/2

See above. I’ll add info to the issue later today ~ish.

>
> I search the Adium .SVG logo:
> - https://github.com/adium/adium/issues/3

I don’t have the answer. Anyone else?

>
> Add a new website here:
> - https://github.com/adium

Does GitHub facilitate this? I think the page is auto-created by GitHub with minimal ability to configure it.

>
> Thanks in advance.
>
> Regards,
>
> Neustradamus

Thanks for consolidating concerns that I’m sure everyone has been feeling.

Asher

[Aerk]

Regarding the SVG logo question in https://github.com/adium/adium/issues/3:

To the best of my knowledge, an SVG version of the Adium logo has never been created. I do have vector art of some sort (can't open right now to see) from the Vectory Ducks Xtras (https://www.adiumxtras.com/index.php?a=xtras&xtra_id=2222), but these are not the official Adium logo, and are not authorized for use as the official Adium logo. I'm not up on the current state of vectorization tech, but it might not be too hard to convert the old pixel art into vectors with decent results.

If we wanted to use the Vectory Ducks, I could see if Sam's old email still works and he would grant us permission for that. Or perhaps someone could ask Adam Betts. I don't know if anyone is still in touch with him...

[Asher Haig]

On Jun 16, 2020, at 3:53 PM, Aerk <smt...@ei8ht.us> wrote:



Regarding the SVG logo question in https://github.com/adium/adium/issues/3:

To the best of my knowledge, an SVG version of the Adium logo has never been created.

Presumably there is/was a vector file for the main logo. Maybe someone still has it? 

I do have vector art of some sort (can't open right now to see) from the Vectory Ducks Xtras (https://www.adiumxtras.com/index.php?a=xtras&xtra_id=2222), but these are not the official Adium logo, and are not authorized for use as the official Adium logo.

Aren’t they all GPL?

I'm not up on the current state of vectorization tech, but it might not be too hard to convert the old pixel art into vectors with decent results.

Doable to high quality with some work, not as easy as a button click. Worth doing if we need it but probably not a good starting point.

[Chris Forsythe]

On Jun 16, 2020, at 4:25 PM, Asher Haig <as...@strong.ai> wrote:



On Jun 16, 2020, at 3:53 PM, Aerk <smt...@ei8ht.us> wrote:



Regarding the SVG logo question in https://github.com/adium/adium/issues/3:

To the best of my knowledge, an SVG version of the Adium logo has never been created.

Presumably there is/was a vector file for the main logo. Maybe someone still has it? 

I doubt it. 

[Eric Richie]

I do have the .psd files from Adam somewhere from the 128x128 icon updates.

I’ll try to dig them up.

-Eric

On Jun 16, 2020, at 2:28 PM, Chris Forsythe <ch...@growl.info> wrote:



[Aerk]

> Aren’t they all GPL?

No, individual Xtras are owned by their creators, with whatever licenses they wanted. In most cases, no license was ever indicated.

[Evan Schoenberg]

The highest resolution images I have are at:

https://adium.im/images/adiumy/

There is definitely not an SVG version; Adam Betts never shared a vector file publicly, and one may not have existed at all.

-Evan

[Eric Richie]

That's from the last email I have from Adam.

-Eric

[Evan Schoenberg]

Thanks, Eric. I’ve added that PSD to the folder I linked below as well as to the full ZIP archive within that folder.

-Evan

<New Adium.psd.zip>

[Gary Kramlich]

Someone sent me this xcf awhile ago too..

--
Thanks,

--
Gary Kramlich <gr...@reaperworld.com>