Looks like itās time for me to clutter the blog again!
To start: Since the last update, Caya has been hard-forked and renamed to
āCardieā (short for ācardinalā),
which at least fits the ābird themeā of libpurple clients.
ā¦ And the nameās fitting, since itās now a fairly functional libpurple client.
:-)
libpurple support
There are a few features not implemented yet, which keeps it behind the XMPP
add-on in terms of functionality, but the core is there: Configuring
and managing accounts for any protocol, joining/creating/leaving rooms,
chatting, sending/receiving your own status, room invitations, managing roster,
purple-side chat commands, etc.
XFS project progress
Hi, I am going to make a short summary of the XFS project work since last post.
Anyway, you can find my post named āGSoC 2021 Project: XFS support progressā on the forum. It records part of the work. Of course, the most is on Gerrit. topic:āxfsā on Gerrit
We could find all remaining patches are merged. But, by the way, not all problems. There is a problem leaving. To be honest, I just learned how to use GDB under linux to debug todayā¦ I lack big project experience before so it is also new skills for me. Now I need to fix it soon and then move to next step quickly, if there is no other changes, it will be attributes read support. So it is also why I choose to write summary at this time. I need to continue my attempt afterwards.
Link to Introductory blog
Link to Progress 1
On my quest to finding a way to trigger my jobs anytime a commit happens in gerrit I was looking into this repo and trying to make it work. I tried using it as a resource but it turns out either itās not public anymore or it was deleted. Then I went through the list of forks in that repo and found this. He claimed to have a base for a somewhat working resource after he made some changes. I cloned his repo and tried building the Dockerfile but it threw some errors. After struggling on it for quite some time and making some minor changes to the files I finally managed to build it and upload it to dockerhub. Then I tried using it as a resource but it failed to fetch my local gerrit repo. Also, the whole thing was written in go which was totally new to me so I started by learning āgoā and after some time when I got the hang of it, I started the debugging phase.
As we get closer to the release of Beta 3, it is important we ensure our translations are updated.
Current State of Translation Work
- As of now, no new language has currently reached over 60% since Beta 2 was released last year.
- Croatian translations are at 58%. If no progress is made, this translation risks being removed from Beta 3!
- Korean, Hindi, Bulgarian, Czech and Norwegian were already under 60% in beta2 and are still under 60%, somewhere between 45% and 60% complete. It would be really appreciated if these translations were made more complete so they can be included with the Beta 3 release.
- Languages that are already available on Pootle, but need a lot more work:
- Punjabi
- Slovenian
- Arabic (unfortunately this translation canāt be displayed due to lack of right-to-left text support in Haiku)
- Serbian (both Latin and Cyrillic versions)
- Macedonian
- Maori
- Low German
- Persian
- Naāvi
Pootle
Translation Cut-off for Haiku's User Interface
The cut-off for interface translations on Pootle remains at 60%.
Itās the end of the first GSoC period, so itās about time I clutter the blog
again!
A good few changes have been made to Cayaā most obviously support for
multi-user rooms and some UI changes. Multi-protocol add-ons are now supported,
the program is oriented around āConversationsā rather than āContacts,ā basic
moderation (kicking, banning, muting) works, etc.
The protocol APIās
expanded because of these general changes, and I donāt think it could be called
āstableā for another couple weeks at leastā I still need to document it, and
some of the new additions might still be consolidated into others.
Hey everyone! I am Hrithik (ritz), You can find about my project in my introductory blog. Hereās what I have done so far.
I started by reading Concourse CI documentation in order to get myself familiarise with ci pipeline and various schema involved in it. I also looked at other resources provided by my mentors i.e. Suhel Mehta @suhel_mehta and Alexander von Gluck @kallisti5 . Below are some links if anyone wants to check out.
Hello, itās time for the May activity report!
Before starting the report, we would like to thank our donors for their donations. Your donations help us cover our expenses and help us reach our goal to hire people to work on Haiku full-time. We would also like to thank all the community for their countless hours of effort of implementing new features, triaging bugs, translating, supporting other users, and spreading the Haiku word all around.
We recently moved our IRC channels from Freenode to OFTC. I almost forgot to register my IRC nickname at the new service, and having just done that, I take the opportunity to describe how thatās done for my fellow - maybe newbie - IRC user.
First, youāll have to configure Vision (or another IRC client) to connect to the OFTC network.
Enter the Network setup and add a new network with the popup menu at the top. Fill in your personal details, including the desired nickname. You can add commands that are automatically executed when connecting to the network, like joining the #haiku channel and identifying/authenticating yourself, see further down.
Introduction
Hey everyone! I am Hrithik Kumar, a sophomore at National Institute of Technology Agartala, India majoring in Computer Science and Engineering (CSE). I am happy to say that I will be working on creating a Coding style checker bot for Gerrit as part of the GSoC 2021 project. My mentors are Alexander von Gluck and Suhel Mehta.
- IRC nick: ritz
- Matrix: ritz (@ritzkr:matrix.org)
Project
Haiku has its own coding guidelines which describe how the code should be formatted. There is a tool (haiku-format tool) for reformatting or checking if code follows these guidelines, but it has to be compiled on the developer machine and then run manually. Now this is extra work but what if it could be automated! Thatās what Iāll be working on this summer i.e. creating a Gerrit bot that would use haiku-format tool for checking whether the patch submitted follows the community guidelines of Haiku and post the report in the comments.
Introduction
Hi! Iām Jaidyn Levesque (jadedctrl on IRC and elsewhere), a 2nd year Computer
Science student. Iāve been using *nixes for several years now, and just
moved over to Haiku as my main OS a little over a year ago. Iām lucky enough to
be a mentee this summer, and Iām excited to get started!
Project
My GSoC project is to modernize Caya, a
multi-protocol chat program. āModernizeā here means a couple different things:
General updates, multi-user chats, and libpurple support. Caya is oriented
around two-member chats, whose protocol is arbitrary, with protocol support
being done through add-ons. It hasnāt seen much activity in the past few years,
so my first goal is to get it running on modern Haiku. Afterwards, chats will be
abstracted to allow for multiple users, enabling protocols like IRC to be
implemented. The last goal, libpurple support, will involve writing a generic
libpurple protocol for Caya.
