Xfce devel packages

[archlinuxcn]

Xfce devel packages

[ykelvis]

All done. And repo is already synced.

[colinkeenan]

Amazing! Thanks

@colinkeenan: Manjaro Linux guys are focusing on xfce, they have xfce 4.11.8 on their repo. If you need that, you can use Manjaro testing branch + Xfce 4.11.8, which equals to Arch stable + xfce 4.11.8 :)

[colinkeenan]

Thanks. I looked at that repo just now. I'll stick with yours though
because it has exactly what I need now and the Manjaro one is missing some.

On Mon, Nov 17, 2014 at 8:38 AM, rtlanceroad [email protected]
wrote:

@colinkeenan https://github.com/colinkeenan: Manjaro Linux guys are
focusing on xfce, they have xfce 4.11.8 on their repo. If you need that,
you can use Manjaro testing branch + Xfce 4.11.8, which equals to Arch
stable + xfce 4.11.8 :)

—
Reply to this email directly or view it on GitHub
#38 (comment).

OK, I ever used manjaro, I would say their xfce4 plugins are the most comprehensive ones. It would be nice if you could tell me what manjaro missed :)

[colinkeenan]

The last 2 on my list are missing. The first one isn't really a plugin, but a replacement for xfwm4 that allows no title on maximized windows. The plugin allows the title & window buttons to be placed on the panel.

xfwm4-titleless-dev
xfce4-windowck-plugin

[zsrkmyn]

@colinkeenan, thank you for your concerning on our repo. And after talking to one of the chiefs of this repo, I'd like to invite to join us and help us maintain this repo. Because the packages added according to your suggestion may lack of maintainer (the maintainer we have now may not use these packages and they may be orphaned later). Of course, you can add other packages most people need to the repo after joining us. We may give some more details if you take this into your consideration :-)
@farseerfc may translate our documentation to English if you need.
You can contact us by replying this issue, or talking to us using IRC. We are in #archlinux-cn at irc.freenode.net, be free to use English~
The chiefs of this repo are @phoenixlzx, @lilydjwg and @felixonmars.
Don't mind my poor English, please ;-)

[colinkeenan]

Thank you. I will accept your invitation to join this repo. I would need @farseerfc translation of the documentation though.

I will contact you by using IRC later, maybe in within a few hours.

[zsrkmyn]

@colinkeenan, I am glad that you can accept our invitation. But don't mind if no one reply you in IRC channel, because it is midnight in China now. You can send email to [email protected] if no one reply you. We may be online mostly during 1:00 to 15:00 UTC.

[farseerfc]

@colinkeenan, welcome to join our repo.

I (aka farseerfc in IRC) will try to translate the documentations of our
toolchains.

In the meantime, you can provide us with some identifications so that we
can authorize you as a packager.

We generally need these information for new packager (as documented here in
Chinese
https://github.com/archlinuxcn/repo/wiki/%E7%94%B3%E8%AF%B7%E7%BB%B4%E6%8A%A4%E8%80%85
):

1. Github account and email address (we already have from your github
   profile)
2. Your preferred username to login to our build server.
3. Your ssh public key
4. (Optional) Your gpg fingerprint, if you would like to sign your package
   before uploading to our repo. We will add this gpg key to
   archlinuxcn/archlinuxcn-keyring later.
5. (Optional) Your user id in bbs.archlinuxcn.org (It is mainly in Chinese).

Please send these information to our mailing list ([email protected]).
Also, a brief introduction of yourself will be appreciated. For example,
your experience on archlinux, your packaging skill and general linux
skill, and so on.

With these information, our repo leaders will create accounts for you.

PS: Most of us live and work in China Standard Time. So if you have any
questions and don't
get answers in our IRC channel, please feel free to ask in our mailing list.

On Tue, Nov 18, 2014 at 1:12 AM, Colin Keenan [email protected]
wrote:

Thank you. I will accept your invitation to join this repo. I would need
@farseerfc https://github.com/farseerfc translation of the
documentation though.

I will contact you by using IRC later, maybe in within a few hours.

—
Reply to this email directly or view it on GitHub
#38 (comment).

---

Jiachen Yang 楊嘉晨
Graduate School of Information Science and Technology, Osaka University
Tel: [phone]
MSN: [email protected]
GMail: [email protected]

@colinkeenan: I talked on #manjaro 1 hour ago, what I got was some of them were ever/now core developers/contributors in xfce4.If I were you, I would like to use manjaro and keep line with upstreams. btw, they said they were using Lunar Linux to host sources codes, So if you are a big fan, maybe use Lunar Linux? That's all about it. You always get a choice, Sir :)

[colinkeenan]

Thanks. That is interesting about Manjaro having xfce4 developers and I looked at Lunar Linux which also looks intersting. However, I've invested a lot of time to understand Arch Linux in the past year and want to continue with that. I switched from Ubuntu to Manjaro, then to Arch. Arch has been more stable for me than either Ubuntu or Manjaro.

I have packages on AUR, both my original ones and ones that I repackage for Arch. I haven't been signing them, but will learn how to do that as well as setup an ssh public key so that I can provide the needed info. I am going forward with becoming a packager for this repo.

：)
On Nov 18, 2014 9:54 AM, "Colin Keenan" [email protected] wrote:

Thanks. That is interesting about Manjaro having xfce4 developers and I
looked at Lunar Linux http://www.lunar-linux.org/about/ which also
looks intersting. However, I've invested a lot of time to understand Arch
Linux in the past year and want to continue with that. I switched from
Ubuntu to Manjaro, then to Arch. Arch has been more stable for me than
either Ubuntu or Manjaro.

I have packages on AUR, both my original ones and ones that I repackage
for Arch. I haven't been signing them, but will learn how to do that as
well as setup an ssh public key so that I can provide the needed info. I am
going forward with becoming a packager for this repo.

—
Reply to this email directly or view it on GitHub
#38 (comment).

[colinkeenan]

I have sent an email with the requested information.