phpMyAdmin Planet phpMyAdmin

I am very happy with my progress today. I managed to place a large dent in the number of tasks this week. I have implemented a small non-obtrusive error notification where you can choose to send an error report.

This opens a modal dialog asking for more info on the report as well as showing the info that would be sent to phpmyadmin’s servers.

Currently there is no way to send the report and the data is not anonymised. Also none of the strings are available for translation. But this is just the first day of the week. I will try to improve the code quality as well as add the remaining functionality by the rest of the week.

Even before the scheduled date for  start coding I started coding on the 12 th of June.

During the past week I was able to remove the places where global variables are used in the sql.php and changed them to use super global variables. Also I renamed certain super global variables such that they better represent their intended use ([0]).

Also I transferred the code in the sql.php which were analyzing the sql.php using regexp to the SQL parser itself ([1] & [2]).

[0] - https://github.com/phpmyadmin/phpmyadmin/pull/415
[1] - https://github.com/phpmyadmin/phpmyadmin/pull/423
[2] - https://github.com/phpmyadmin/phpmyadmin/pull/428

My plans for the coming week is to further refactor the sql.php script using extract method.

I started with my GSoC project last week. To begin with, I started to write Unit Tests for Charset Conversions.

Today is the official starting date for my gsoc project with phpmyadmin. My tasks this week include catching exceptions and collecting necessary info as well as showing a modal dialog with the required info and asking for the user’s permission to send the report while observing the stored configuration settings related to it.

I still donot know who to collect that information in the minified js code. I have asked my mentor for help as well as petitioned for unminified js in production. I googled and couldn’t find a good solution for the problem other than source maps which sadly are not yet implemented in most browser versions.

I will start with the other tasks now and even take on some tasks from next week and leave this part till I know how to solve it. Hopefully I will stumble upon the answer soon.

• Key accomplishments last week

• Tasks in the upcoming week

• Key accomplishments last week

In the last week, I finished the scheduled tasks. Refactor following files:

server_collations.php : https://github.com/phpmyadmin/phpmyadmin/pull/410

server_status_monitor.php : https://github.com/phpmyadmin/phpmyadmin/pull/421

https://github.com/phpmyadmin/phpmyadmin/pull/431

 

• Tasks in the upcoming week

As scheduled, this week I will refactor the following server view files:

server_databases.php

server_replication.php

According to GSOC 2013 timeline, the coding period begins tomorrow. It's quite exiting as we get to do some hands on coding. I have pretty much completed reading documentation and getting myself familiarize with the code. Meanwhile I pulled merge requests for a couple of bugs and those fixes were incorporated to the code.

I am going to implement 'Improve relational view interface' feature during the first week. This is based on feature requests RFE #1283, RFE #1233 and RFE#175 from the feature request tracker. I've done some investigations related to these features during the last week.

With the implementation choosing the foreign column would be made a two step process. First the user chooses the foreign table from the table drop down which would filter the column in the columns drop down accordingly. Hence choosing the correct column would be much easier. Finally, the relational system would be enhanced to support cross database relations. Relational view interface would facilitate adding/editing these relations with an additional drop down to chose the database.

I will use 'relView' branch of my repository to implement this feature. However it is still empty, I will make a commit when the new code is stable.

In this week, I focus on the following two parts:

• Schema designer (libraries/schema)

• Transformations (libraries/plugins/transformations)

I am very happy for being accepted to GSoC at phpmyadmin. My task is an error reporting system for the javascript code in phpmyadmin. I will be using this blog to comment on my progress on my phpmyadmin project.

I am actually in the architecture design stage now with the server component. I will most likely use Cakephp as my MVC framework of choice, unless the phpmyadmin developers agree on me using Ruby on Rails as my framework. While I believe that it is much easier to develop using Rails due to the gems available that do almost anything you may imagine, however not using php as a language would be problem for maintainability down the line.

I will probably publish an updated schedule soon since the current one doesn’t distribute the efforts across the entire period.

This summer I was selected as a GSOC student to contribute to phpMyAdmin. I am really thankful to Google and phpMyAdmin for giving me this opportunity. My project is to refactor the SQL executor and Column's structure manipulation code.

Short description:
The goal of this project is to refactor the SQL executor and Column's structure manipulation code. To improve readability, reduce complexity, and to improve maintainability I am suggesting to refactor the SQL executor and Column's structure manipulation code using better approaches. The code will be refactored according to various code refactoring techniques mainly focusing on componetization and extract method.

My project proposal can be found here: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/scnakandala/1

My github repository can be found here: http://github.com/scnakandala/phpmyadmin

In the coming weeks starting from 17 th of June I will be working on this project and I will use this blog to record the status of my work and to share interesting things that I find.

I have been selected for Google Summer of Code 2012, and I will be contributing for phpMyAdmin. My project is to refactor the SQL executor and Column's structure manipulation.

Short description
The goal of this project is to refactor the SQL executor and Column's structure manipulation code.
To improve the readability, reduce the complexity, and to improve maintainability I am suggesting to refactor the SQL executor and Column's structure manipulation code using better approaches. The code will be refactored according to various code refactoring techniques mainly focusing on componentization and extract method.

My Project Proposal can be found here: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/scnakandala/1

• Key accomplishments last week

• Tasks in the upcoming week

Hi everyone,

This is my first post here. I will use this blog to communicate the progress of my GSoC 2013 project  and hopefully even afterwards to write about some technical stuff.

First of all here are some details about the project. My project is titles "phpMyAdmin Interface Improvements" and as the name suggests I plan to implement an array of small to medium scale features during this summer. My mentor for this project is Isaac Bennetch and I look forward to cooperate with him in order to implement the feature requests with high usability.

More details about my project can be found here. Here is an extraction from my proposal to give you a high level overview of the project.

"phpMyAdmin is quite a matured project with more than 14 years of history behind it. It possesses almost all the major features required for a database administrative tool and there is very little that can be added in this front. However there is always room for small and medium scale new features. This is evident from the huge backlog of feature requests requested in the project’s feature request tracker. In this proposal, I propose a number of small to medium scale improvements chosen from the feature request tracker, majority of them selected by the developers of the project themselves and listed in the GSoC 2013 project ideas list."

• Key accomplishments last week

In the last week, I finished the scheduled tasks. Refactor following files:

server_binlog.php : https://github.com/phpmyadmin/phpmyadmin/pull/404

server_plugins.php : https://github.com/phpmyadmin/phpmyadmin/pull/405

 

• Tasks in the upcoming week

As scheduled, this week I will refactor the following server view files:

server_collations.php

server_status_monitor.php

Hi, this is Ayush. This year, I have been selected in GSoC 2013 to work under phpMyAdmin. My project for the same is Automated Testing which involves creating unit tests for the existing codebase and increasing the code coverage.

One of our main courses this semester is the Software Engineering course. Each tutorial group was a fictional company and divided further into 4 teams. Each tutorial group had a real client and a real project to create by the end of the semester. The aim of the course is to teach us collaborative development techniques as well as agile development.

A competition between the companies was created and the winner would be the one who best followed the process and delivered the best end product. All the projects were web development related and targeted the middle east, specifically Egypt.

The development was divided into 2 sprints of length 2 weeks. The project was divided into stories in a backlog. They were given points according to difficulty and were assigned to one of the 15 developers in the company. Every story had to be well documented, with unit tests and a sequence diagram describing it. The code had to follow code conventions and the story had to be peer reviewed and verified before merging it into the master branch.

Our project was a game with a purpose. The aim was to crowdsource arabic translations and then provide statistics to developers who are looking for the best translations targeting a certain country or age group. We also created a script to automate the translation of your page based on the country of the user of your website. The public repo can be found on github.

The competition was fierce but we persevered and as the title already revealed we won. The course was a resounding success and many would-be developers learnt the ropes of how to create a large software project successfully.

Hi, Following is my time schedule about server view refactor. because I have two exams this week, after that I can spend full time on this project. Thanks

I will go though all the server view files.

June 1 – June 16: Refator following files: (also the included file in PHP)
server_binlog.php server_plugins.php

server_collations.php server_status_monitor.php

June 17 – June 30: Refator following files: (also the included file in PHP)
server_databases.php server_replication.php

server_engines.php server_status_variables.php

July 1 – July 14: Write unit tests for your newly refactored functions.
July 15- July 28: Refator following files: (also the included file in PHP)
server_export.php server_status.php

server_import.php server_status_advisor.php

July 29 – August 11: Refactor following files:
server_privileges.php server_status_queries.php

server_sql.php server_variables.php

August 12 – August 25: server_privileges.php server_status_queries.php
server_sql.php server_variables.php

August 26 – Sept 6: Refator following files: server_common.inc.php server_privileges.lib.php server_variables_doc.php

Sept 7 – Sept 16: Write unit tests for your newly refactored functions.
Sept 16 – Sept 23: Buffers & Some other refator & Final evaluations

• Schema designer (libraries/schema)
• Import (libraries/plugins/import)
• Transformations (libraries/plugins/transformations)
• DBI (libraries/dbi)
• Relations (libraries/relation*)
• SQL parser/analyzer (libraries/sqlparser, libraries/parse*)
• IP allow/deny rules (libraries/ip_allow*)
• Table operations (libraries/Table*)

In the firstly week, (0602-0608)

I have finished:
1. submited the needed materials to Google
2. Warm up on PMA code
3. communicate with Mentor (Michal) about the task split.

Doing now:
I will focus on the first part of code:
- DBI (libraries/dbi)


Hope to have a good result this week!


Adam

the final work split:
===================Adam ==================

Following is my First week’s work, I will try my best to finish it!

• Tasks in the upcoming week (June3~June 9)

1. Prepare the forms that Google need

2. Refactor following files:

server_binlog.php

server_plugins.php

 

Today, I sent a pull request to PMA.

https://github.com/phpmyadmin/phpmyadmin/pull/403

It is about refactor server_status.php: 

Update (3Jun2013) : An improved version the git subtree module is available, now with a config file to define your subtrees and imported projects. There is an updated blog post describing how to install and use it.

Did you ever want to merge an external git tree with yours, while keeping the commit history? Or do you want to create a new git repository from a folder in your project, keeping the history?

Then the git subtree module is what you need. It let's you import a complete git repo (with commit history) into your project, and add the files to a folder you specify.

For example :

$git subtree add --prefix=other_project \
     git://github.com/your_tree/your_project.git master

imports the master branch of your git repository located in git://github.com/your_tree/your_project.git into the folder other_project.

If you make changes to this imported project and you want to push them back to the original project, you can use this :

$git subtree push --prefix=other_project \
     git://github.com/your_tree/your_project.git master

BTW: the subtree module is not part of the core git package. So if you want to use it, you will have to install the module first.

Download the git subtree module and extract it, or clone it :

$git clone https://github.com/apenwarr/git-subtree

In the git-subtree directory, run

$chmod u+x install.sh

and as root :

#./install.sh

This will copy the git subtree module to the git script folder. You can now use the git subtree module.

I have written about the git subtree module before.
It has been improved, to allow defining your subtrees and imported projects in a config file, in order to update them without having to specify the repo url and branch every time you push to or pull from an imported project.

So, first you need to setup the subtree :

$git subtree add --prefix=other_project \
     git://github.com/your_tree/your_project.git master

It imports the master branch of a git repository located in git://github.com/your_tree/your_project.git into the folder other_project of your git repo.

Then, create a file .gittrees in the root folder of your git repo :

[subtree "other_project"]
    url = git://github.com/your_tree/your_project.git
    path = other_project
    branch = master

Now that the subtree is defined in .gittrees, if you make changes to this imported project and you want to push them back to the original project, you can use this :

$git subtree push --prefix=other_project

Or if you want to update the imported project with changes from the original project, you can use this :

$git subtree pull --prefix=other_project

You can also push all changes in imported projects to the original projects, with

$git subtree push-all

It will push all changes to projects that are defined in the .gittrees config file.
Pull changes from all defined subprojects is done with :

$git subtree pull-all

BTW : All subtree commands must be run in the root folder of your git repo.

BTW2: the subtree module is not part of the core git package. So if you want to use it, you will have to install the module first.

Clone the subtree project :

$git clone https://github.com/helmo/git-subtree

In the git-subtree directory, run as root :

#./install.sh

This will copy the git subtree module to the git script folder. You can now use the git subtree module.

Today, I Summit material to Google, including:

1. Tax form

2.  Student Card

 

I think I can starting working now.

In this blog, I try to mark something I did while I apply for PMA.

from the code coverage link: http://ci.phpmyadmin.net/job/phpMyAdmin/cloverphp/?



we should discussion every folder. some folders are unneeded to contain on code coverage.

Hi guys,

Thanks for coming my blog. Here is my home for GSOC2013: Refactoring Server View on PMA

Following is my proposal:

Name

xmujay

Chinese Name: Bin Zu(祖斌)

Location

• Country : China
• Time Zone : GMT + 8

Education

Undergraduate, Beijing University of Science and Technology

Email / IRC / Jabber

xmujay@gmail.com

Synopsis

While reading some server view source code of PMA, I found that the source code has some problems: not easy read, not easy reusable, full of long function, full of long file. Because PMA is a big project which is developed by a lot of Programmers from all over the world, we should enhance the maintainability to let more developers join in. From other side, in a project’s life cycle  sometimes we need to re-factor the code if the code starts smelling bad and it’s hard to maintain and even harder to add new features. By enhancing the readability and maintainability of code, re-factoring makes it easier for us to deal with the code. This idea aims to re-factor the code on “Server view” and make the code easy to understand and easy to reuse. It won’t involve changing the existing functionality of these scripts, nor would it introduce new functionality.

Benefits to the users

Because this project won’t involve changing the existing functionality of these scripts, nor would it introduces new functionality  the project would not benefit the common users directly, but it will be a big benefit to our developers. With these re-factoring, developers can use the existing codes by calling or extending the same functions and make the develop process more easily.

Project Details

 I will re-factor the code in the following aspects:

1.         Render the HTML element at once (using Response::AddHtml instead of echo)

2.         Fix HTML and PHP mixture

3.         Fix code indention

4.         Use better variable for readability

5.         Fix PHP tags and ugly code in the code base

6.         Make the source code better structured.

7.         Reduce Long lines & Long functions & Long files

8.         Comments: Making the code self-documenting by mitigating the need for many inline comments.

9.         Introduce OOP concept the PMA code, so that the code can be reused easily.

10.       The location of a particular function or code block is also important, so functions/code blocks will be moved to appropriate places/scripts if required.

11.       There are also many nested if-else blocks in the code. So, removal of any unnecessary

If time available, I will re-factor the following issues:

1.         Increase the corresponding Unit testing.

2.         Better performance, UI and user experience

The server view contains several files with prefix: server_. We should re-factor them one by one. They also include some library files.

1. 1.    the display PHP files: starting with server_ prefix.

server_binlog.php      server_plugins.php         server_status_monitor.php

server_collations.php  server_privileges.php      server_status_queries.php

server_databases.php   server_replication.php     server_status_variables.php

server_engines.php     server_sql.php             server_variables.php

server_export.php      server_status.php

server_import.php      server_status_advisor.php

Take server_ privileges.php for example:

• This file is a very large file and there are HTML and PHP mix tags in this file. So this file is not structured well. Therefore this code is not readable. We can separate these HTML tags and PHP tags. Then we can nicely split PHP snippet into several functions, then use this PHP functions in HTML tags. It will improve the readability of the code. The code will be very smart by using set of re-factoring method. Then we can write unit test for these functions to make sure that functions work properly.
• And other issue is that the render code is using “echo”. We should render them at once, so before render, we should collect the HTML element. There is no need to echo in either function. Let both of them return a Html string, call those functions in the place you need them and echo  the result there. Or feed it to the addHtml() method from the Response class that is already defined in every file behind an accessible page.
• See for more info on how to use this. http://wiki.phpmyadmin.net/pma/Generating_pages_and_ajax_responses_in_pma4

We should refactor it:

• All the functions are re-factored one by one considering their functionality, coding conventions, and readability of the code and re usability of the code.
• Library files will return the specific output or render HTML codes at once (at the end of the function) without rendering the HTML codes everywhere inside the function itself.

1. 2.    Backend files.

server_common.inc.php  server_privileges.lib.php  server_variables_doc.php

• These three PHP files also somewhat ugly, because of they contain lot of code with conditions, loops. It is better if we clean the code to make it more understandable and structured by reducing number of nesting levels of conditions, implementing several functions to do the same thing in a smart way without changing the behavior of the application.

 Take server_privileges.lib.php for example:

• This file contains huge ‘if’ conditions like thousands of lines. It should re-factor to reduce the complexity by implementing several functions. And we can improve the readability of the source code.

Deliverables

After this project, reusable, re-factored, easy readability code will deliver to PMA, so that the development process will be easier and effective.Because this project won’t involve changing the existing functionality of these scripts, nor would it introduces new functionality  the project would not benefit the common users directly, but it will be a big benefit to our developers. With these re-factoring, developers can use the existing codes by calling or extending the same functions and make the develop process more easily.

Hi all,
I am Adam Kang. this blog is to track my GSOC2013 with PhpmyAdmin. (http://www.phpmyadmin.net/)
https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/adam_kang/1

PMA is a popular web based database management tool. It usually undergoes new releases, bug fixes, new feature development and refactoring. Since the PMA production code is changed frequently and our code is finished by developers from all over the world, in order to guarantee the production quality, it is very necessary to run Unit testing on Jenkins (Hudson). Unit Tests have several benefits to us. It allows us changing code quickly under full testing. By running unit tests, a developer can identify whether his latest changes to the code base has broken anything. Unit Tests can also help new developers really understand the design of the code and it can give our developers visual feedback about which lines are covered. From PMA CI Page, Currently, the code coverage of PMA is 18.3%. More code coverage means more guarantee to production.
Goal:
1. Increase the code coverage to a reasonable percentage (80%)
2. Set up the necessary scripts to automate unit testing.
3. Help other developers to set up their unit test cases.
4. Functional test case to cover render issue

Strategy: we should cover core code to a high level (90%) at firstly and then spent some time on the other stuff.

Hope to have a great code summer with PMA.

phpMyAdmin is pleased to announce that it has accepted 6 students/projects for Google Summer of Code 2013 :

• AJAX error reporting : Mohamed Ashraf
• Automated Testing : Adam Kang
• Automated Testing : Ayush Chaudhary
• Interface improvements : Kasun Chathuranga
• Re-factoring: server view : Bin Zu
• Refactoring: SQL Executor, Column's Structure Manipulation : Supun Nakandala

Details about the accepted projects can be found on the wiki.

Congratulations, good luck and happy coding to all the students.
phpMyAdmin looks forward to their contributions to the project.

As student application period of Google Summer of Code 2013 is over, it's time to look at proposals we got for phpMyAdmin.

First of all we got slightly less proposals than in past years. This is probably related to the fact that we still heavily focus on code cleanup this year and this is definitely not that interesting topic as adding new features. I think quality has also slightly improved and this time we received no bogus or spam proposals.

Also as usual, people tend to leave submission for very last date (though not that much as in past years):

Quite unsurprisingly the most interesting topic seemed to be interface improvements, though it is quite wide. You can see how other topics were frequent in following chart:

Please note that the numbers are not 100% accurate as some proposals really did not fit into above categories.

Anyway we're just working on evaluation and will finalize it in upcoming days. Of course you will know the results from Google on May 27th.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

About 45 interested students showed up for the Google Summer of Code 2013 info session that was organised at Ghent University on Monday, April 15th 2013 in the Faculty of Engineering in the Plateau building.

First there was an general introduction on what Google Summer of Code (GSoC) is, explaining the goal of the program, the benefits for the students and an overview of the timeline. This was followed by a few Open Source organisations that will participate in this year's GSoC, presenting themselves and potential projects to work on, and a few students who took part in past versions of GSoC, sharing their experiences with the audience. This turned out to be a nice mix of information and different experiences that gave a good view for the attending students on what to expect from applying for and participating in GSoC.

Some useful advice that was spread :

• Put enough time in the preparation of your project proposal. Your future mentors will review this and will base their decision on accepting you mostly on this proposal. Make sure you explain well what you plan to do, how you plan to do it, and how much time you will spend on each part. Be as detailed as possible.
• Be active in the community of the organisation you want to work with. This shows the mentors that you are really interested. Don't be afraid to ask questions, or to participate in a discussion on the IRC channel or mailing list. It helps when your name rings a bell when the mentors are going through all the project proposals.
  The sooner you start with this, the better. Follow the mailing list and try submitting a few patches. It was suggested that you choose an org for next year already and contribute to it, as a preparation for GSoC 2014 (if there would be one).
• Choose a project you like. If you get accepted you'll spend almost 3 months working full time on it, so it helps if the programming language, developing environment, code base and your project are something you are comfortable with. This does not mean that you should choose a too easy project, there can be some challenge. That will keep it interesting for you. Just find something you can chew but is challenging enough to keep you going.
  It was mentioned that having some proficiency with the programming language you will be working with is usually a good point, but one of the organisations (ESUG) mentioned that learning a new language (SmallTalk in their case) can be a nice experience as well.
• It is an interesting experience, that will give you some real world development experience, will get you introduced in the Open Source community and looks nice on your CV.

The evening was closed by a reception with room for the students to talk to the speakers and ask questions.

Thanks to the Google Open Source Programs Office for the promotional material, the Open Source organisations (phpMyAdmin, SAGE, ESUG, MuseScore, Debian and Samba) and previous GSoC students (Jasper Van der Jeugt (worked on Haskell) and Sander Bogaert (worked on K9 mail)) for their talks and sharing their experience, and to the student associations (VTK, Zeus WPI, Ceneka) and UGent for their help in organising the event.

Weblate 1.5 has been released today. It comes with lot of improvements, especially in performance, reporting and support for machine translations.

Full list of changes for 1.5:

• Please check manual for upgrade instructions.
• Added public user pages.
• Better naming of plural forms.
• Added support for TBX export of glossary.
• Added support for Bitbucket notifications.
• Activity charts are now available for each translation, language or user.
• Extended options of import_project admin command.
• Compatible with Django 1.5.
• Avatars are now shown using libravatar.
• Added possibility to pretty print JSON export.
• Various performance improvements.
• Indicate failing checks or fuzzy strings in progress bars for projects or languages as well.
• Added support for custom pre-commit hooks and commiting additional files.
• Rewritten search for better performance and user experience.
• New interface for machine translations.
• Added support for monolingual po files.
• Extend amount of cached metadata to improve speed of various searches.
• Now shows word counts as well.

You can find more information about Weblate on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user. Ready to run appliances will be soon available in SUSE Studio Gallery.

Weblate is also being used https://l10n.cihar.com/ as official translating service for phpMyAdmin, Gammu, Weblate itself and others.

If you are free software project which would like to use Weblate, I'm happy to help you with set up or even host Weblate for you.

Filed under: English Phpmyadmin Suse Weblate | 0 comments | Flattr this!

phpMyAdmin 4.0-rc2 is out and if your want to have your language in final release, it's last moment to start working on translation.

So let's look at which translations are at 100% right now (new ones are bold):

• Catalan
• Czech
• Danish
• Dutch
• English (United Kingdom)
• Estonian
• French
• German
• Greek
• Portuguese (Brazil)
• Slovenian
• Spanish
• Swedish
• Turkish

Almost complete:

• Galician
• Polish
• Russian
• Simplified Chinese

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

Hackweek 9 is over and it's time to share what I've done on Weblate during that.

I think everything went quite well and Weblate is now ready for 1.5 release. I'm slowly deploying it on my installations (unfortunately this release migration will need some noticeable downtime for bigger installations) and everything seems to work fine so far. I believe this is possible thanks to massive test coverage - all important code is covered by testcases.

So what you can expect in 1.5 release? The most visible change is probably new machine translation support, providing support for way more backends and allow you to plug in own services as well. The other changes include word counting (what might give you more idea how much work is remaining) or fancy progress bars in all places (they used to be available for translations only).

From the other side, Weblate can now run custom scripts to pre-process translations before commit, what can be used for various things from generating byte compiled files to sorting or cleaning up the translation files.

Also Weblate should be now much faster - there were dozen of optimizations done, leading to much lower press on database server.

If you want to see more detailed work progress, check Hackweek project page or Weblate changelog.

PS: In case no problems appear, Weblate 1.5 should be released on Sunday.

Filed under: English Phpmyadmin Suse Weblate | 0 comments | Flattr this!

phpMyAdmin has been accepted for Google Summer of Code 2013. So if you are a student and thinking about how to spend this summer, you might want to join us.

This year we will have fresh mentor blood and we have prepared dozen of ideas, so in case you are interested, it's really the time to start to work on your application. We require you to contribute before GSoC, so that we can see you can handle the code and our tools. All details you might need are available in our applicant guide.

Our requirements might sound strict, but without them, we would drown in hundredths of applications with no clue how to decide, so do your homework and prepare perfect application. If you have any questions, get in touch with us on mailing list and get ready for April 22th, when you can submit the application.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

phpMyAdmin has in last year received various useful features, which are not that well known. I've decided to give them some promotion before releasing phpMyAdmin 4.0.

The server monitoring part is already present since phpMyAdmin 3.5, but some of the parts were further improved in 4.0.

Server monitor (as you can see on picture above or on demo server) allows you to follow server status in real time. Besides predefined charts, you can choose to follow any of MySQL server status variables or some system parameters.

If you see something weird in the charts, you can select interval and inspect slow or general query log (if you have enabled it). This can help you finding most problematic queries for your server.

Advisor (on picture above or on demo server) is another way to improve server performance - it comes with extensive set of rules, which can help you tuning performance for your workload. Your server has to be running for significant time to give some reasonable recommendations (so don't expect these on the demo server, which is restarted quite often). However it is still recommended to read server documentation before doing any adjustments, as the setting might have some side effects, which will affect your workload as well.

Of course these are not magic pill to cure your unresponsive server, but can help you a lot in finding possible bottlenecks.

Filed under: English Phpmyadmin | 1 comments | Flattr this!

phpMyAdmin 4.0-rc1 is out and it's really time to work on translations if you want them to be ready for final release..

So let's look at which translations are at 100% right now (new ones are bold):

• Catalan
• Czech
• Danish
• Dutch
• English (United Kingdom)
• Estonian
• French
• Greek
• Portuguese (Brazil)
• Spanish
• Swedish
• Turkish

Almost complete:

• Galician
• German
• Polish
• Russian
• Simplified Chinese
• Slovenian

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

Zin om deze zomer $5000 te verdienen met een vakantiejob? Lijkt het je wel iets om vanuit thuis te werken wanneer het je uitkomt? Wil je een echte bijdrage leveren aan open-source software? Google maakt dit mogelijk dankzij de Google Summer of Code!

Op maandag 15 april organiseren Zeus WPI, VTK en CenEka een introductieavond rond Google Summer of Code. Dieter Adriaenssens, mentor van het phpMyAdmin-project, introduceert het concept en de procedures. Daarna komen enkele mentors hun projecten voorstellen, afgewisseld met studenten die hun ervaringen van vorige jaren delen. Achteraf kan je eventuele vragen aan de mentors stellen of gewoon gezellig napraten bij een drankje op de afsluitende receptie.
Deze introductie vindt plaats in de Jozef Plateau-zaal in de Plateau en begint om 19:00. Iedereen is welkom! Om een idee te hebben van het aantal aanwezigen vragen we om op deze pagina in te schrijven.

Ben je zelf een mentor of heb je ooit meegedaan en ben je geïnteresseerd om je project voor te stellen of ervaringen te delen op deze avond? Laat iets weten!

Wanneer : maandag, 15 april 2013, vanaf 19:00
Waar : Jozef Plateauzaal, faculteit Ingenieurswetenschappen UGent, Plateaustraat 22, Gent
Gratis toegang, maar best op voorhand inschrijven.

You might have already noticed that there is Hackweek 9 coming next week. At SUSE we will get pizzas, icecream and other nice stuff, but most importantly we can spend the week on hacking anything we want.

Same as last year, I want to spend most of my Hackweek on Weblate, nice crowdsourcing tool for translations. The major goal is to finish 1.5 release, what should not be that hard. The most challenging bits for new machine translation interface are already implemented, and the rest is pretty much only tweaking of existing code.

Another thing we want to explore is possibility of using Weblate for openSUSE translations. Currently they are mostly kept in SVN, what is blocker for using Weblate, but we will see what can be done there.

Filed under: English Phpmyadmin Suse Weblate | 0 comments | Flattr this!

Test Driven Development (TDD) is cool! And useful. By writing tests for a method or class before implementing that class, work on that class is not finished, until all defined tests pass. Provided of course, that you wrote good and extensive tests, that cover as much as possible all the different cases and possibilities of how the method/class should behave.
And the upside is, that you can be sure that all your methods/classes keeps working later in the development process, because you have tests that continuously check if all classes keep behaving like you expect them to. If you would change something that would break the expected functionality of a method/class, then at least you will know, because some tests will fail. That's a few bug reports avoided!

Next round of phpMyAdmin 4.0 translation status report is coming.

So let's look at which translations are at 100% right now (new ones are bold):

• Catalan
• Czech
• Dutch
• English (United Kingdom)
• Estonian
• French
• Greek
• Spanish
• Swedish
• Turkish

Almost complete:

• Chinese (China)
• Danish
• Galician
• German
• Polish
• Portuguese (Brazil)
• Russian
• Slovenian

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 4 comments | Flattr this!

phpMyAdmin's website just got small facelift from me. The motivation was to make navigation easier in some parts and to come up with consistent color schema.

This time changes are not that major as in past - basically just CSS changes and few minor changes to HTML code. The structure of the website is still pretty much same and I did not touch the texts at all.

Unfortunately this is still not responsive design, so it will not look that good in small or huge resolutions, but I hope to get back to this later.

Filed under: English Phpmyadmin | 2 comments | Flattr this!

This night you might have noticed that some services like hosted Weblate or phpMyAdmin wiki being quite flaky.

It was caused by DDOS attack which pretty much busted firewall and thus made unable to open new connections. In the morning when I've realized this, I introduced another breakage by too strict filtering on firewall :-). However now everything should be back to normal.

Filed under: English Phpmyadmin Weblate | 0 comments | Flattr this!

For some time, Weblate was showing avatars for users. Just as I've discovered Libravatar - free and federated alternative to Gravatar, I thought it would be better replacement.

Quickly looking at their website, it seems that they transparently provide all avatars from Gravatar as well, so the migration seems to be pretty much painless. Basic replacement to use their server is just matter of changing base URLs, however to support federated behavior, you have to install pyLibravatar. Weblate in Git now supports both these ways.

While implementing the client side, I did also setup my own instance of Surrogator to provide avatars for some of my domains. Surprisingly this worked fine without problems, but let's see how much used this will actually become.

Filed under: English Phpmyadmin Weblate | 2 comments | Flattr this!

Next round of phpMyAdmin 4.0 translation status report is coming.

So let's look at which translations are at 100% right now:

• Czech
• Dutch
• English (United Kingdom)
• Greek
• Spanish
• Swedish
• Turkish

Almost complete:

• Chinese (China)
• Danish
• Estonian
• French
• Galician
• German
• Polish
• Portuguese (Brazil)
• Russian
• Slovenian

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

Next round of phpMyAdmin 4.0 translation status report is coming.

So let's look at which translations are at 100% right now (some changes this week due to new strings to translate):

• Czech
• Dutch
• English (United Kingdom)
• French
• Greek
• Spanish
• Turkish

Almost complete:

• Danish
• Estonian
• Galician
• German
• Polish
• Russian
• Slovenian
• Swedish

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

As you have probably already noticed, Google Summer of Code 2013 has been officially announced. As usual, we want to participate with phpMyAdmin.

We really want good students to participate, so our selection process will be again slightly stricter than in last years. So if you want to participate as a student on phpMyAdmin, please check our applicant guide. The most important thing is that we expect you to show knowledge of the code before being accepted and fixing some bug for upcoming 4.0 release is great opportunity to start with that!

Also student themselves usually don't bring new ideas, so it's pretty much on the organization to come with projects it would like to see. We are currently collecting these on our wiki. We will most likely add some new ones to the list as well, so feel free to get in touch if you have some brilliant idea. Also voting on feature requests might help us to choose what users see as most important improvements.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

Next round of phpMyAdmin 4.0 translation status report is coming.

So let's look at which translations are at 100% right now (some changes this week due to new strings to translate):

• Czech
• Dutch
• English (United Kingdom)
• French
• Greek
• Russian
• Spanish
• Turkish

There are also several languages which need just few strings to be complete:

• Danish
• Estonian
• Galician
• German
• Japanese
• Polish
• Portuguese (Brazil)
• Slovenian
• Swedish

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

Last weekend, was FOSDEM 2013, two days of talks about Open Source, almost 500 in total, spread over more than 20 developer rooms.

It started on Friday night, at the Delirium café in the center of Brussels, where a few hunderd developers had gathered for beer and socialising. I planned to meet some people, but finding them was not an easy task. Ironically, modern day tools like SMS proved useless : by the time the messages I sent reached them (hours later), I had already found them.

After a nightly walk to the hotel and a short night, it was time for the real stuff. First the opening talk by FOSDEM staff, with some practical info about the conference : the new logo, location of rooms and buildings, wireless network, sponsors, catering, first aid, devrooms, lightning talks and main track speakers; finished by the FOSDEM dance, which was a bit more complex than previous years.

Looking at the list of talks I have attended (with more than 20 simultaneous talks at any time during the conference, it was impossible to go to all 500 of them), I'll mention some highlights :

• I went to quite a few talks about legal and licensing issues. Over the years I've come to realise this is an important part of the Open Source world. Choosing an Open Source license and publishing your work under it, being it software, hardware design, or other creative work, is one thing, making sure the license terms are not violated, is another. Although some talks were informative, some raised more questions than were answered.
  For example, if I publish my software under an Open Source license as a European citizen, will European law protect my copyright and license terms? If the software is used in the EU, this would probably be the case. But what about other regions in the world?
• Maintaining a kernel subsystem : informative talk and good speaker. Although it was about maintaining a kernel subsystem, the methods he used, can be used to maintain any Open Source project.
• Welcome to the Symfony2 World  gave an overview of the current state of the Symfony 2 framework, with some history and what components and possibilities it has.
• Vehicular traffic estimation through bluetooth uses a Raspberry Pi and some Open Source tools, to track traffic connecting to bluetooth capable devices. Nice application of the Raspberry Pi.
• What's new in BIND 10 and Samba4 : both telling a story about rewriting the previous software to come to a newer, better and improved version. Samba 4 will now support SMB3 protocol and Active Directory.
• One of the most interesting talks explained what the actual problem is with UEFI SecureBoot, who the different players are (from users, over system builders, to hardware and OS vendors) and how the problem can be solved.
  Basically : Windows 8 requires UEFI Secureboot to be enabled (UEFI replaces the old BIOS), otherwise it will not start up. Secureboot ensures that the OS being started is valid, by checking it's signature with one stored in the UEFI chip. As such, this is not bad, but when you want to boot an OS that is not signed by a key, or the key is not present in the chip, it is impossible to start this OS, making dual booting linux/Windows 8 very difficult.
  Luckily some intiatives are done to make the dual booting possible, with the most recent one : Linux Foundation obtained a Microsoft key, making it possible to boot a linux distro on a device were Windows 8 is installed. (this happened after FOSDEM, so it was not mentioned during the talk)
  Of course, it is still possible to boot Linux, or any other OS, on a device with UEFI, when you don't want to use Windows 8. Then you can just disable the SecureBoot option.

And last but not least, I had my own presentation about the Present and future of phpMyAdmin in the MySQL and Friends devroom. About 50-60 people attended, although it overlapped with the final key note and was one of the last talks at FOSDEM. The talk went well, small hickup during the demo and there were some questions afterwards.

It was a nice weekend, lots of interesting talks, meeting a few current and previous team members of the phpMyAdmin and some people I've met at the GSoC mentor summits. Still only 51 weeks to go before the next FOSDEM.

Next round of phpMyAdmin 4.0 translation status report is coming.

So let's look at which translations are at 100% right now (no change this week):

• Czech
• Dutch
• English (United Kingdom)
• Galician
• Greek
• Russian
• Spanish
• Turkish

There are also several languages which need just few strings to be complete:

• Danish
• Estonian
• French
• German
• Japanese
• Polish
• Portuguese (Brazil)
• Slovenian
• Swedish

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

If you missed the talk about the Present and future of phpMyAdmin at FOSDEM 2013, you can get the presentation here. Only slides, so without the demo's. ;)

Summary of the talk : What's new in phpMyAdmin and what's coming up? An overview and some demos of the new features and changes in the current release (3.5) and what to expect in the upcoming 4.0 release.

FOSDEM 2013 is over and it's time to look what interesting I have seen there on Sunday.

Sunday was supposed to start for me with L20N, but it was postponed to 13:00 as the presenters weren't on time. I could have used one more hour of sleep, but at least I spent some time on coding.

Detect merge conflicts in realtime was quite interesting talk, though I was pretty surprised that the conflict detecting does not at all care about underlying version control system, but does purely file based guesses.

The Hardening MySQL talk pretty much described why security in MySQL sucks and what you should do to make it secure. Quite good introduction to the topic, but not much new information for me.

Introduction of Firefox OS, was quite nice demo showing they have something working, though it had some problems with flaky network on FOSDEM. Looking forward to see phone being sold, though it will probably not be something I'd buy.

To add some fun, I've stayed on systemd, Two Years Later presentation, which gave some summary of what is currently in systemd and where it wants to go. Still it did not move systemd from category of "I don't care as long as it works".

Now followed delayed L20N talk - it showed new Mozilla's effort for localization. Which is quite powerful and has nice features, on the other side it put's quite more load to translators - now they would have to understand some basics of programming as well to be able to use the new features (or not so new ones as plurals). Their motivation is to remove localization effort from developers, but I'm not really convinced it will work nicely.

After some meetings and lunch, I went to LibreOffice: cleaning and re-factoring a giant code-base, which showed some challenges LibreOffice has to take and how they dealt with that. I think it's pretty great job done and I'm looking forward to new releases.

Being GNOME user, I could not skip Has the GNOME community gone crazy?. It of course tried to tell that they did not :-).

Last, but not least my friend Dieter from phpMyAdmin had talk Present and future of phpMyAdmin. He listed some of the new features, demoed 3.5 and 4.0 version (of course the demo of 4.0 version broke due to some caching). Even when the talk had quite unpleasant timing, it has attracted some people and they even asked few questions.

This years FOSDEM was again great and looking forward to be there next year.

Filed under: Debian English Phpmyadmin Suse Weblate | 2 comments | Flattr this!

FOSDEM 2013 is over and it's time to look what interesting I have seen there on Saturday.

First of all the most important for me is to meet people. As usual, I came with SUSE folks, but it's not that unusual to meet people from company where you work :-). I've met some current and former phpMyAdmin developers and surprisingly I've met few Weblate users or people who consider using it on their project. This gave me some important feedback and one of first thing you will see in near future is remade Weblate website to give more information about some of it's unique features. As for the talks, I think I've managed to visit quite lot of them.

How we made the Jenkins community explained some ways Jenkins has used to build good community - mostly focused on extensibility of the code and having everything as an extension, but with some focus on social things as well (and important thing that with Git people are not that motivated to join the team).

Better software through user research was about various way to gather information of what your users hate on the software. It was pretty interesting, though many of that can not easily be used on small scale free software product.

OSS code goes in and never comes out talk focused about licensing issues of various software as a service platforms. As I've never used Amazon cloud or such, it was quite surprising how these behave in relation to GPL and actually made me thing more about AGPL and attend related panel discussion later.

An Integrated Localization Environment is Mozilla approach to online translation, quite different than anything we have before, but mostly for reasons which were explained later on Sunday talk on l20n. Maybe reverse ordering of these would make it easier to understand the motivation.

Scale your Jenkins build pipeline automatically to minimize test time was not that useful as I thought - increasing test speed by buying EC2 instances and pushing part of the work to them is not something what will help me in near future.

Trends in Open Source Security explained what is going on in distributions security, mostly focused on Redhat (but touching Debian as well). It has some interesting thoughts about sharing the information between vendors, so let's see if it will really work in future.

QML’s many faces showed some other ways to use QML besides using QtQuick. Some uses were quite interesting, though I'm not really fan of creating yet another buildsystem based on it.

Panel Discussion: GNU Affero General Public License, version 3 was last thing I've visited on Sunday and it was really interesting to listen all that opinions on AGPL. Still I was not confirmed to consider switching to this license.

Filed under: Debian English Phpmyadmin Suse Weblate | 0 comments | Flattr this!

Next round of phpMyAdmin 4.0 translation status report is coming.

So let's look at which translations are at 100% right now:

• Czech
• Dutch
• English (United Kingdom)
• Galician
• Greek
• Russian
• Spanish
• Turkish

There are also several languages which need just few strings to be complete:

• Danish
• Estonian
• French
• German
• Japanese
• Polish
• Portuguese (Brazil)
• Slovenian
• Swedish

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 0 comments | Flattr this!

A few more days and FOSDEM 2013 starts again. I've been looking forward to this since I left FOSDEM 2012. ;)

A lot of talks and presentations to go to, some people to meet (again), but most importantly : I will do a talk about phpMyAdmin!

If you are at FOSDEM and want to know more about the Present and future of phpMyAdmin, then come to room H.2214 (MySQL & Friends devroom) on Sunday, February 3rd, 2013 at 17:00.

I will talk about the new features in the current version (3.5.x) and what you can expect in the upcoming version 4.0.0.

Hope to see you there!

Finally, phpMyAdmin packages for Debian and Ubuntu do not lag much behind upstream. Today, I've prepared packages for yesterday released bug fix release 3.5.6.

For Debian users, the package should be soon available in experimental (sorry no uploads to unstable during freeze).

Ubuntu users, can use my phpMyAdmin PPA. After dozens of comments and no help offered, I've still decided to be nice to Ubuntu users and adjusted the package so that it should work on Lucid as well. The downside is that, unlike in Debian, the package includes bundled copy of many PHP and javascript libraries.

PS: As soon as Debian is not frozen or 4.0 is officially released, I will start uploading 4.0 to experimental. My current bet is that 4.0 release will come earlier.

Filed under: Debian English Phpmyadmin | 0 comments | Flattr this!

Weblate 1.4 has been released today. It comes with lot of improvements, especially in configurability, admin interface and usability.

Full list of changes for 1.4:

• Fixed deleting of checks/comments on unit deletion.
• Added option to disable automatic propagation of translations.
• Added option to subscribe for merge failures.
• Correctly import on projects which needs custom ttkit loader.
• Added sitemaps to allow easier access by crawlers.
• Provide direct links to string in notification emails or feeds.
• Various improvements to admin interface.
• Provide hints for production setup in admin interface.
• Added per language widgets and engage page.
• Improved translation locking handling.
• Show code snippets for widgets in more variants.
• Indicate failing checks or fuzzy strings in progressbars.
• More options for formatting commit message.
• Fixed error handling with machine translation services.
• Improved automatic translation locking behaviour.
• Support for showing changes from previous source string.
• Added support for substring search.
• Various quality checks improvements.
• Support for per project ACL.
• Basic unit tests coverage.

You can find more information about Weblate on it's website, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. You can login there with demo account using demo password or register your own user. Ready to run appliances will be soon available in SUSE Studio Gallery.

Weblate is also being used https://l10n.cihar.com/ as official translating service for phpMyAdmin, Gammu, Weblate itself and others.

If you are free software project which would like to use Weblate, I'm happy to help you with set up or even host Weblate for you (this will be decided case by case as my hosting space is limited).

Filed under: English Phpmyadmin Suse Weblate | 0 comments | Flattr this!

With release of first alpha for phpMyAdmin 4.0, it's time to resurrect my regular translation status posts.

So let's look at which translations are at 100% right now:

• Czech
• English (United Kingdom)
• Galician
• Greek
• Spanish
• Turkish

There are also several languages which need just few strings to be complete:

• Danish
• Dutch
• French
• German
• Russian
• Slovenian
• Swedish

As you can see, there is still lot of languages missing, this might be your opportunity to contribute to phpMyAdmin. Also you are welcome to translate phpMyAdmin 4.0 using translation server.

If your language is already fully translated and you want to help as well, you can translate our documentation as well.

Filed under: English Phpmyadmin | 0 comments | Flattr this!